ansi 92

[Guest]

Is it my imagination or is the ansi 92 standard that is available in access
2003 only half way correct. The way I see it is - the ole db or odbc driver
for jet still expects to see certain access specific things in a sql query.
Dates are a prime example. You still can't use qoutes around dates. You
still have to use # enclosures. Makes certain portability a pain or
conversions a little pain or a little time consuming to correct.Any comments
on this ? or am I wrong ? If I am correct, any hopes on this actually being
100 % compatible with a new native driver or at least an upgraded ole db
driver for access ?

Thanks,
Jason

 

[david epsom dot com dot au]

If you are using # for dates, you aren't using the "ansi 92"
interface.

Please give an example of how you are trying to use the
ansi 92 interface.

If I'm wrong, the chances of it being corrected are close to zero.

(david)

 

[Guest]

In most SQL queries I have done in VB6 and SQL Server, the dates are inputed
like a text command - with single quotes. Access of course if the # sign.
I'll have to try it again, but I am sure the regular ANSI 92 is single quotes
for dates - just like a text string.... I'll check again.

Thanks,
Jason

 

[david epsom dot com dot au]

Yes, Ansi 92 uses single quotes.

Access supports both an "ANSI 92" and a "JET"
syntax. Which you get depends on how you
approach it. The two are not mixed: you either
get one or the other.

Are you using Access forms and Reports? Or how
are you trying to use Access?

(david)