We have an MFC/DAO application which is encountering all sorts of trouble
accessing an .MDB file which links tables via an ODBC data source (SQL
Server 6.5).

The same tables and queries seem to work fine if run directly from Access
via the same MDB file, so I believe that the tables and links are all set
up correctly. The original .MDB file (prior to upsizing to SQLServer and
then linking the tables) also works great in both places.

Turning on ODBC tracing indicates that DAO/Jet is supplying an invalid
window handle to ODBC on the SQLDriverConnect call, but this happens only
intermittently. Has anyone seen anything like this? Is there a workaround?

Thanks

--
Randy Baker (remove Z from address in email replies)