Board index Database

?This SQL statement won't work -- Microsoft.Jet.OLEDB.4.0 has reserved words?

?This SQL statement won't work -- Microsoft.Jet.OLEDB.4.0 has reserved words?

Post by Al Mac » Fri, 21 Apr 2000 04:00:00



I have found that the SQL command

  select * from Descriptors order by Type, Descriptor

will not work when I use the Microsoft.Jet.OLEDB.4.0 provider.  After much
trial and error,  I've found that it fails because one of the fields is
called "Descriptor".  If I change the field name to something else, it works
OK.

Note that this works fine when MSDASQL;Driver={Microsoft Access Driver
(*.mdb)} is the provider.

I also found that naming a table "Index" is a no-no with the jet provider.
Are "Descriptor" and "Index" reserveds word?  If so, where can I find a list
of the other reserved words?

 
 
 
Top

?This SQL statement won't work -- Microsoft.Jet.OLEDB.4.0 has reserved words?

Post by Al Mac » Sat, 22 Apr 2000 04:00:00


I have found that the SQL command

  select * from Descriptors order by Type, Descriptor

will not work when I use the Microsoft.Jet.OLEDB.4.0 provider.  After much
trial and error,  I've found that it fails because one of the fields is
called "Descriptor".  If I change the field name to something else, it works
OK.

Note that this works fine when MSDASQL;Driver={Microsoft Access Driver
(*.mdb)} is the provider.

I also found that naming a table "Index" is a no-no with the jet provider.
Are "Descriptor" and "Index" reserveds word?  If so, where can I find a list
of the other reserved words?

 
 
 
Top

?This SQL statement won't work -- Microsoft.Jet.OLEDB.4.0 has reserved words?

Post by Gabriel Knizni » Sat, 22 Apr 2000 04:00:00


If you use reserved words, enclose them between square brackets. I can't
remember where I saw a list of reserved words, but you can trust your common
sense when choosing names.

Gabriel Kniznik


Quote:> I have found that the SQL command

>   select * from Descriptors order by Type, Descriptor

> will not work when I use the Microsoft.Jet.OLEDB.4.0 provider.  After much
> trial and error,  I've found that it fails because one of the fields is
> called "Descriptor".  If I change the field name to something else, it
works
> OK.

> Note that this works fine when MSDASQL;Driver={Microsoft Access Driver
> (*.mdb)} is the provider.

> I also found that naming a table "Index" is a no-no with the jet provider.
> Are "Descriptor" and "Index" reserveds word?  If so, where can I find a
list
> of the other reserved words?

 
 
 
Top

?This SQL statement won't work -- Microsoft.Jet.OLEDB.4.0 has reserved words?

Post by Al Mac » Sat, 22 Apr 2000 04:00:00


I didn't think that Descriptor would be reserved, but perhaps anything that
starts with DESC (as in DESCENDING) will fail.

The thing that bothers me most is that what fails depends on the provider.
I would prefer more standardization.


> If you use reserved words, enclose them between square brackets. I can't
> remember where I saw a list of reserved words, but you can trust your
common
> sense when choosing names.

> Gabriel Kniznik



> > I have found that the SQL command

> >   select * from Descriptors order by Type, Descriptor

> > will not work when I use the Microsoft.Jet.OLEDB.4.0 provider.  After
much
> > trial and error,  I've found that it fails because one of the fields is
> > called "Descriptor".  If I change the field name to something else, it
> works
> > OK.

> > Note that this works fine when MSDASQL;Driver={Microsoft Access Driver
> > (*.mdb)} is the provider.

> > I also found that naming a table "Index" is a no-no with the jet
provider.
> > Are "Descriptor" and "Index" reserveds word?  If so, where can I find a
> list
> > of the other reserved words?

 
 
 
Top

?This SQL statement won't work -- Microsoft.Jet.OLEDB.4.0 has reserved words?

Post by Russ E. R » Thu, 27 Apr 2000 04:00:00


TYPE is the reserved word in this case I believe. Type it as [Type] in the
Order by clause.
--
Russ E. R.
DMCI-modis
Director, Software Development



Quote:> I have found that the SQL command

>   select * from Descriptors order by Type, Descriptor

> will not work when I use the Microsoft.Jet.OLEDB.4.0 provider.  After much
> trial and error,  I've found that it fails because one of the fields is
> called "Descriptor".  If I change the field name to something else, it
works
> OK.

> Note that this works fine when MSDASQL;Driver={Microsoft Access Driver
> (*.mdb)} is the provider.

> I also found that naming a table "Index" is a no-no with the jet provider.
> Are "Descriptor" and "Index" reserveds word?  If so, where can I find a
list
> of the other reserved words?

 
 
 
Top

1. Problems with acess Win NT 4.0+ Microsoft.Jet.OLEDB.4.0 + Null Field

Hi,

I have a program using ADO with jet engine 4.0 and when doing the following
query I get 0 records........
but with jet engine 3.51 , or with access, using the same query I get 1324
records!

Does anybody know if this is a bug?
If so... is there any solution?

This is the query: "select count(*) from Movimentos where Num_Env=Null"

Thanks in advance!
Paulo Cabrita
Portugal

2. Using IN function in MS Access 2000

3. Microsoft.Jet.OLEDB.4.0 Provider not working with Access 97 MDB

4. ORACLE SYBASE DBA Miami FL

5. Command.Execute with parameter works with ODBC provider, fails with Microsoft.Jet.OLEDB.4.0

6. Help with Access Database Please!!

7. Parameter ?_1 has no default value (Provider=Microsoft.Jet.OLEDB.4.0) on UPDATE statement

8. Command.Execute with parameter works with ODBC provider, fails with Microsoft.Jet.OLEDB.4.0

9. Jet SQL Error - Reserved word?

10. can't install Microsoft.OLEDB.JET in my setup

11. SQL Jet Reserved Words missing in Help file

12. HELP;HELP;Seek method doesn't work wiht Jet.OLEDB.4.0


All times are UTC
Board index