Network Error Access Compile
Contents |
be down. Please try the request again. Your cache administrator is webmaster. Generated Wed, 19 Oct 2016 17:10:18 GMT by s_ac4 (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 compile access database forum that you want to visit from the selection below. Results 1 to 5 of 5
Msaccess.exe /decompile
Thread: Error Accessing File. Network Connection May have been lost. Tweet Thread Tools Show Printable Version Subscribe to this Thread… Search Thread error accessing file network connection lost excel 2010 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 http://answers.microsoft.com/en-us/msoffice/forum/msoffice_access-mso_other/access-2010-error-accessing-file-network/9ae829b3-f7c6-4f7c-b137-188363167aa4 lost. I am using Access 2000 and received the message: "Error accessing file. Network connection may have been 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 http://www.dbforums.com/showthread.php?305300-Error-Accessing-File-Network-Connection-May-have-been-lost 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 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
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 http://stackoverflow.com/questions/7480536/access-compile-error-on-ado-recordset-open-possible-reference-issue Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow 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 Access Compile Error on ADO recordset open - error access possible reference issue? up vote 1 down vote favorite As a bit of background we are a small Access software house with 10 + years of working with over 150 Customer sites. We have 5 different apps. Our main product has over 30,000 lines of vba and about 400 forms and reports. I am telling you this background as we think we know our vba and access. error accessing file We normally work in Access 2003, but compile and distribute in Access 2k, Occasionally we will work in Access 2002 , 2007 and 2010. We have run into a problem where in the last week or so some (not all) of our applications will not allow us to compile on some machines. Last week we had a problem with one windows7 box where Access 2003 was regularly crashing (that seemed to rectify itself on a compile on an XP machine and amove to worko solely in Access 2k), this week a second win 7 box is having problems with a specific app (will not compile - error on opening an ADO recordset). This seems to have started after an install of Access 2010. This seems now to have "spread" to other machines. We think its most likely an ADO reference issue but it is weird as other apps as other apps with the same references on the same PC and the same lines of code complile OK. What we have tried so far, all machines are up to date with latest MS patches. We have uninstalled and reinstalled the various versions of access. It seems to be worse (and