Microsoft Access Error Accessing File
Contents |
be down. Please try the request again. Your cache administrator is webmaster. Generated Thu, 20 Oct 2016 15:44:34 GMT by s_wx1126 (squid/3.5.20)
been lost. If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. Results 1 to 5 of 5 Thread: Error Accessing File. Network Connection May have been lost. Tweet Thread Tools Show Printable Version Subscribe to this Thread… Search Thread Advanced Search Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode 02-26-02,00:53 #1 lpdds View Profile View Forum Posts Registered User Join Date Feb 2002 Posts 11 Unanswered: Error Accessing File. Network Connection May have been lost. I am using Access 2000 and received the message: "Error accessing file. Network connection may have been http://answers.microsoft.com/en-us/msoffice/forum/msoffice_access-mso_other/access-2010-error-accessing-file-network/9ae829b3-f7c6-4f7c-b137-188363167aa4 lost". The file is now corrupt. I have a back up but I made many changes after I made the back up. I read in the forums that Microsoft has a fix for this but it is not public. Does anyone know what this fix is? Microsft has an article in the knowledge base but it explains how to prevent the problem, not how to fix it. Please help. Thank you, Leonard Patella Reply With Quote 03-10-02,00:33 #2 William Hooper View Profile View Forum Posts Registered http://www.dbforums.com/showthread.php?305300-Error-Accessing-File-Network-Connection-May-have-been-lost User Join Date Mar 2002 Location Calgary, Alberta Posts 5 Hi, I just had this same problem and could not resolve it on my own. So I ask the Lord for His help based on that verse in the Bible which says "If any of you lack wisdom, let him ask God who gives to all men liberally." He led me to the right resources, and the problem is solved. Create a new database and import all the tables, modules, queries and other objects into it. Next, open a code window and click on the Debug menu, then the compile option. Clean up all the errors you encounter either by deleting the offending code or (if you need it and it's still under construction) comment it out. When you get a clean compile, save the database and exit. Make a backup copy at this point (I usually create a new folder with the date as part of the name to store it in). This issue results from a conflict between Access and a .DLL from Office XP or Visio 2002 documented in the MS Knowledge Base. It crops up specifically as a result of importing objects from another Access database (or, in my case, from adding a class to my .MDB on the fly). That puts part of the database into a non-compiled state and generates the error. Compile and backup frequently! Here is the information I uncovered: Two ARTICLES in here: both deal with "Error Accessing File" error Second article has a reference to ho
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the http://stackoverflow.com/questions/18342287/cant-eliminate-access-corruption company Business Learn more about hiring developers or posting ads with us Stack Overflow http://www.techrepublic.com/article/access-2000-error-network-connection-may-have-been-lost-might-indicate-vbe6dll-conflict/ Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Can't eliminate Access corruption up vote 3 down vote favorite My firm's Access database has been having some serious error accessing problems recently. The errors we're getting seem like they indicate corruption -- here are the most common: Error accessing file. Network connection may have been lost. There was an error compiling this function. No error, Access just crashes completely. I've noticed that these errors only happen with a compiled database. If I decompile it, it works fine. If I take an uncompiled database and compile it, it works fine -- until the next error accessing file time I try to open it. It appears that compiling the database into a .ACCDE file solves the problem, which is what I've been doing, but one person has reported that the issue returned for her, which has me very nervous. I've tried exporting all of the objects in the database to text, starting with a brand new database, and importing them all again, but that doesn't solve the problem. Once I import all of the objects into the clean database, the problem comes back. One last point that seems be related, but I don't understand how. The problem started right around the time that I added some class modules to the database. These class modules use the VBA Implements keyword, in an effort to clean up my code by introducing some polymorphism. I don't know why this would cause the problem, but the timing seems to indicate a relationship. I've been searching for an explanation, but haven't found one yet. Does anyone have any suggestions? EDIT: The database includes a few references in addition to the standard ones: Microsoft ActiveX Data Objects 2.8 Microsoft Office 12.0 Microsoft Scripting Runtime Microsoft VBScript Regular Expressions 5.5 vba ms-access ms-access-2007 share|improve this question edited Aug 20 '13 at 18:36 asked Aug 20 '13 at 18:20 Jeff Rosenberg 2,740832
United States Australia United Kingdom Japan Newsletters Forums Resource Library Tech Pro Free Trial Membership Membership My Profile People Subscriptions My stuff Preferences Send a message Log Out TechRepublic Search GO Topics: CXO Cloud Big Data Security Innovation Software Data Centers Networking Startups Tech & Work All Topics Sections: Photos Videos All Writers Newsletters Forums Resource Library Tech Pro Free Trial Editions: US United States Australia United Kingdom Japan Membership Membership My Profile People Subscriptions My stuff Preferences Send a message Log Out Software Access 2000 error, "Network connection may have been lost," might indicate Vbe6.dll conflict In Access 2000, receiving the message "Error accessing file. Network connection may have been lost" may not really reflect a connection issue. Instead, it may merely reflect the hazards of patching security holes over time. The solution is another patch, of course. By Mark Kaelin | June 16, 2004, 12:01 AM PST RSS Comments Facebook Linkedin Twitter More Email Print Reddit Delicious Digg Pinterest Stumbleupon Google Plus Problem For security reasons, it's imperative that we keep Microsoft Office Suite software patched and up to date. However, patching applications, especially software that is as pervasive and complex as Office, can lead to unexpected and often frustrating consequences. Because security updates from Microsoft are deployed piecemeal, in fits and starts, conflicts and incompatibilities may arise and cause certain operations, which worked in the past, to fail in the present. Unfortunately, the reasons for these failures are not usually obvious. If you've received the error message "Error accessing file. Network connection may have been lost" while working with Access 2000, you may have the issue described in Microsoft Knowledge Base Article 304548. Without getting into the mundane details, the basis of the problem is a conflict between Access 2000 and version 6.3.91.8 of the Vbe6.dll. This conflict prevents certain code modules from compiling and running. The failure of the code results in the seemingly unrelated error message. For example, you may see this error when you're trying to add a combo box to an existing Access 2000 database, as was described in this Tech Q&A question by Highlander718. If the conditions described in Knowledge Base Article 304548 are met, performing all of the proper steps to install your combo box would result in the above error message—an annoyingly frustrating situation to say the least. Solution Oddly enough, this obscure error has a very obvious and straightforward solut