Hi,



I've got an Access 2000 database that solely consists of linked tables

that are actually stored in a MySQL database. Access is exhibiting strange

behaviour after it's been left idle for a while with a table window open;

upon trying to close the table window, the following message appears:





This action will reset the current code in break mode.



Do you want to stop the running code?



* To halt the execution of the program so the Module window can be

closed, select Yes.

* To leave the code in the current stats, select No.





The thing is, I don't have any module windows open or any code running

(there are no modules in the database). Clicking Yes on this message has

no effect; the message disappears and reappears instantly. Clicking No 

removes the message window but leaves the table window open; trying to

close it again brings up the message again. If I try to exit Access

without closing the table window first, Access hangs and has to be

killed from the task manager.



Has anyone else experienced anything like this when using linked tables?

Is this a timeout issue? It only happens when Access has been left idle

for a while, so is the MySQL/Access connection being dropped, then Access

gets confused because of this?



Cheers,



Dave.



(for those of you that are interested: this is related to the P2P

site - part of our back-end uses a MySQL database, and my colleagues

and I use Access to view and update tables as it seems the easiest

option for a lot of cases).



-- 

David Long <davidl@w...>

Wrox Press - Programmer to Programmer(tm)

http://p2p.wrox.com/