Kevin said:
MGFoster wrote:
...
Now that is interesting. What I'm trying to do is to develop queries to
go against Access through ODBC, not use the Access program itself. Is
there a way to invoke this SQL Server Compatible Syntax through ODBC?
I noticed, for example, that when I tried to use a date constant in the
form 'mm/dd/yy', it didn't work although one help file that I read
mentioned that dates in single quotes did work (mentioned ANSI-92).
Since I'm much more familiar with SQL Server (T-SQL), it would be very
helpful to be able to write in that dialect for my work against an
Access database.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I don't know how to, or if you can, inform ODBC that the db is in ANSI
92 compliance. I believe the compliance has to be invoked by Access
when it builds the database (creates tables/queries).
Not all T-SQL statements can be used in JET-SQL (or SQL92 for that
matter - T-SQL having many enhancements over SQL92 & JET-SQL).
In JET dbs dates are usually delimited by the hash-mark:
#mm/dd/yyyy#. Only if the db is created in ANSI-92 compliance will
you be able to use single-quotes to delimit dates.
- --
MGFoster:::mgf00 <at> earthlink <decimal-point> net
Oakland, CA (USA)
-----BEGIN PGP SIGNATURE-----
Version: PGP for Personal Privacy 5.0
Charset: noconv
iQA/AwUBQFPAV4echKqOuFEgEQI+CgCdGB8r8hpB//NCXrNuGFn8AYvVmTQAnjzl
5B6AVtMYQkrphKu1wRwKtn3q
=eMu1
-----END PGP SIGNATURE-----