Im affraid this might be MicroSoft's bug on their software. Similiar kind of effect has happend for us too, but with MySQL.. Access2002 is actually quite unstable to use with anything else than MS-SQLServer and even that has its own problems.
I hope they'll fix the thing some day, but it is possible that you'll need to pay for the fix since it might be included to the next version. My goal is to move away from Access to PHP-based net interface and I would recommend you'll do the same.
By the way, Access does refresh open ODBC queries by time to time (setting adjustable from Access's settings) and the problem might be related to it.
Antti
Hi,
We are using Access 2002 w/ the latest Postgresql ODBC driver to connect to
a postgres database and make updates. If a linked table (or query) is left
open for an hour or more w/o making changes and then closed, a general
protection fault results (see event log entry below). There are multiple
people making edits on the same database around the same time.
Is there a timeout setting or such in the ODBC driver that can cause this?
Has anyone else had a similar experience?
Faulting application msaccess.exe, version 10.0.3409.0, faulting module
unknown, version 0.0.0.0, fault address 0x0000176d.
Thanks in advance for your help,
Kevin Plouffe