Charlotte Foust
cfoust at infostatsystems.com
Tue Aug 5 09:58:48 CDT 2003
As I mentioned in an earlier post, the hotfix was only available until they rolled it up into SR-3. It is no longer available separately. Charlotte Foust -----Original Message----- From: Erwin Craps [mailto:Erwin.Craps at ithelps.be] Sent: Monday, August 04, 2003 8:26 PM To: Access Developers discussion and problem solving Subject: RE: [AccessD] The Dreaded"ErrorMessage:ErrorAccessingFile.NetworkConnection May Have Been Lost." Then please tell me where the path is beause, I did not find any article telling me there a patch available. -----Oorspronkelijk bericht----- Van: Charlotte Foust [mailto:cfoust at infostatsystems.com] Verzonden: dinsdag 5 augustus 2003 0:25 Aan: Access Developers discussion and problem solving Onderwerp: RE: [AccessD] The Dreaded "ErrorMessage:ErrorAccessingFile.NetworkConnection May Have Been Lost." Without the patch, clicking Save would not necessarily help you. I encountered the bug in its full glory early in Office 2000 history and toasted several databases until I discovered the cause and got the patch. Charlotte Foust -----Original Message----- From: Erwin Craps [mailto:Erwin.Craps at ithelps.be] Sent: Monday, August 04, 2003 2:06 PM To: Access Developers discussion and problem solving Subject: RE: [AccessD] The Dreaded "Error Message:ErrorAccessingFile.NetworkConnection May Have Been Lost." I confirm, never solved.... When importing code in modules or forms/reports I always click "save" first in VBA. I'm not sure if compiling is sufficiant, I always click save. Never found a solution in MSKB Erwin -----Original Message----- From: Charlotte Foust [mailto:cfoust at infostatsystems.com] Sent: Monday, August 04, 2003 11:54 PM To: Access Developers discussion and problem solving Subject: RE: [AccessD] The Dreaded "Error Message: ErrorAccessingFile.NetworkConnection May Have Been Lost." All I can say is that SP3 has fixed it on the machines I've encountered. Believe me, the situation without the patch was infinitely worse! Charlotte Foust -----Original Message----- From: Robert Gracie [mailto:Subscriptions at servicexp.com] Sent: Monday, August 04, 2003 1:40 PM To: Access Developers discussion and problem solving Subject: RE: [AccessD] The Dreaded "Error Message: Error AccessingFile.NetworkConnection May Have Been Lost." The problem as stated in KB 304548 (http://support.microsoft.com/default.aspx?scid=kb;en-us;Q304548) is indeed what is going on, the MAJOR Issue here is,....it is not fixed with SP3. (would anyone like to confirm this..) So just a warning to others that have version 6.3.91.8 of the Vbe6.dll, and are using A2K, even with the patch. Don't, whatever you do, import or "save as" an object and close that db, with out compiling first. It will trash your db... Robert Gracie www.servicexp.com -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Susan Geller Sent: Monday, August 04, 2003 3:08 PM To: Access Developers discussion and problem solving Subject: RE: [AccessD] The Dreaded "Error Message: Error Accessing File.NetworkConnection May Have Been Lost." Robert, I'm jumping into the middle of this thread and can't find the beginning, but here's an idea -- it won't necessarily get your old work back, but it may prevent it in the future. It's advise I got from MS a while back when I was having this problem: Check vbe6.dll - if have version number 6.3 and have Access 2000, then need hotfix for 2000 which installs a newer version of MSAccess.exe for 2000 - version # 9.0.0.6013. Lower versions should be fine. Have to get hotfix from MS. --Susan -----Original Message----- From: Robert Gracie [mailto:Subscriptions at servicexp.com] Sent: Sunday, August 03, 2003 11:59 AM To: Access Developers discussion and problem solving Subject: [AccessD] The Dreaded "Error Message: Error Accessing File. NetworkConnection May Have Been Lost." Well it just happened to me, and I have about 11 hours worth of work that maybe lost (is lost from what I have been reading) The problem is that I did have the "Office 2000 Service Pack 3" installed. So since MS says this will stop the problem from happening in the future, and obviously it does not, how can I protect myself.. Such a pain....!!!! What cause the corruption.... "Save As" some reports..... Any pearls of wisdom?? Robert Gracie www.servicexp.com _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com