Charlotte Foust
cfoust at infostatsystems.com
Mon Mar 3 19:07:00 CST 2003
Thanks for the suggestion, John. Unfortunately, in our case, Outlook doesn't hang, only Access. Interestingly enough, on some of our machines, if Outlook is minimized, the Access doesn't hang, but if it is open on the desktop, even if Access is on top, then Access hangs when it tries to reconnect to its own back end. I'm going to rewrite the code to reattach the tables and see if new code using DAO (there are reasons) but written entirely from scratch, will behave the same way. Charlotte Foust -----Original Message----- From: John Ruff [mailto:papparuff at attbi.com] Sent: Monday, March 03, 2003 4:07 PM To: accessd at databaseadvisors.com Subject: RE: [AccessD] Access XP and 97 hang on reattaching linked tables under WinXP Charlotte, I had a similar problem when trying to send email with Access2K/XP under either Win2K or WinXP (with or without Redemption; it didn't matter if Outlook was open or not; but I didn't have the current db opened in a 2nd DAO worspace). I found that if there was an error in my send Email procedure that the instance of Outlook that was initiated through the send Email procedure was not closing. Consequently, two instances of Outlook was running. The next time I tried to send an email through the Email procedure, Access would sometimes hang, but Outlook would always hang. Using the Task Manager to stop all instances of Outlook and/or Access did not always make things right so I ended up doing a reboot to get everything to work properly. I found through trial and error that the Outlook resources initiated in the Email procedure were not being released. When I changed the procedure to insure that these resource were released, even if an error occured, my problem was resolved. Evidently, in my case anyway, Win2K and WinXP do not like two instances of Outlook running. If you are using the code I sent you, but you modified it so that the releasing of resources in not after the SendEmail_Exit Label, or that you've removed the error trapping portion, or you've modified the error trapping whereby you are bypassing the releasing of resources, that might be your culprit. John V. Ruff - The Eternal Optimist :-) Always Looking For Contract Opportunities www.noclassroom.com <http://www.noclassroom.com/> Live software training Right over the Internet Home: 253.588.2139 Cell: 253.307/2947 9306 Farwest Dr SW Lakewood, WA 98498 "Commit to the Lord whatever you do, and your plans will succeed." Proverbs 16:3 -----Original Message----- From: accessd-admin at databaseadvisors.com [mailto:accessd-admin at databaseadvisors.com] On Behalf Of Charlotte Foust Sent: Monday, March 03, 2003 2:39 PM To: AccessD at databaseadvisors.com Subject: [AccessD] Access XP and 97 hang on reattaching linked tables under WinXP We're beating our heads against this one. Under certain specific circumstances, both Access XP and 97 will hang running under WinXP. The circumstances are that Outlook is running (either 2000 or XP) and you toggle to the Outlook application during a portion of the operation when Access is trying to reattach files using an instance of the current database opened in a second DAO workspace. I'm trying to track down anything on this problem and haven't had much luck. There are articles about the ODBC drivers in multithreaded environments, but they seem to apply more to SQL Server links and are supposed to be fixed by the latest installation of Jet 4.x. Not on my machine, they aren't. Does anyone have any more information on this issue? We're also getting reported hangs after an email is sent by our application on a client's WinXP machine, but we haven't been able to replicate that. The primary suspect in both cases is Outlook, even though we use the Redemption library to bypass the direct MAPI calls. Suggestions? Charlotte Foust -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://databaseadvisors.com/pipermail/accessd/attachments/20030303/13196636/attachment-0001.html>