ODBC connection fail

[Justin Kerr]

Hello,

I need some help with connecting Access 2000 to a 32-bit
ODBC data source. We recently upgraded this ODBC
accounting program. I have recreated the data source and
re-linked the tables, but now my queries work fitfully at
best.

Basically, I would like to know whether this happens
because of a problem with the connection to the data
source or with the relationships I have set up for my
queries.

The queries tend to fail when I have entered two or more
criteria to search by. The error message is 'ODBC
Driver/ISAM Error (#4)'. The error says I have entered an
invalid filter in one of the fields of the tables in the
original in the ODBC source, although I have not done so.
Sometimes I also get an 'ODBC Driver Manager/Function
Sequence Error (#0)'.

Could it be the size of the tables in the data source are
too large for Access?

Thanks

Justin

PS I am posting this here because I cannot find an ODBC
newsgroup. Apologies if this is in the wrong group.

 

[Tim Ferguson]

Basically, I would like to know whether this happens
because of a problem with the connection to the data
source or with the relationships I have set up for my
queries.

Lots of strange things happen when you move away from Jet toward normal
standards. For example, the wildcards for LIKE change from "*?" to "%_";
rules for single and double quotes change; and all VBA functions and user-
defined functions are immediately invalid. Valid alternatives are
available, but vary depending on your server software.

It is likely that your favourite WHERE clauses have become illegal,
probably in several different ways.

....

PS I am posting this here because I cannot find an ODBC
newsgroup. Apologies if this is in the wrong group.

For details on difficult SQL queries, try m.p.a.apdsqlserver

B Wishes


Tim F