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. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Error Accessing File. Network Connection may be lost.
I get the subject error when attempting to create, delete, and modify VBA
code. I also cannot create a VBA procedure because of the error: Microsoft Access failed to create the Visual Basic module '|,' I don't know what either of the errorss means. I have created modules from scratch, and I don't get these errors. These errors occur on .mdb applications that were created previously. Any suggestions?? 10SNUT -- 10SNUT |
#2
|
|||
|
|||
You have a serious corruption problem! See this link:
http://support.microsoft.com/default.aspx?scid=kb;[LN];304548 "10SNUT" wrote: I get the subject error when attempting to create, delete, and modify VBA code. I also cannot create a VBA procedure because of the error: Microsoft Access failed to create the Visual Basic module '|,' I don't know what either of the errorss means. I have created modules from scratch, and I don't get these errors. These errors occur on .mdb applications that were created previously. Any suggestions?? 10SNUT -- 10SNUT |
#3
|
|||
|
|||
"10SNUT" wrote in message
I get the subject error when attempting to create, delete, and modify VBA code. I also cannot create a VBA procedure because of the error: Microsoft Access failed to create the Visual Basic module '|,' I don't know what either of the errorss means. I have created modules from scratch, and I don't get these errors. These errors occur on .mdb applications that were created previously. Any suggestions?? This error represents a particular kind of corruption in your VB project. Are you using Access 2000, but not patched with SP3? If so, see this KB article describing the nasty bug that may have bitten you: http://support.microsoft.com/default.aspx?scid=kb;[LN];304548 If that article does match your circumstances, then Office 2000 SP3 fixes the bug, but that won't repair your corrupted database. You'll have to resort to a backup, or else try importing all objects to a new database -- some objects probably won't import, and you'll have to recreate them from scratch. When you do import the objects, unless you've applied the service pack, it is *crucial* that you compile and save the project before closing the database. If that article does not apply to you, your corruption probably has another cause, but you may still have to take the same steps to recover from it. -- Dirk Goldgar, MS Access MVP www.datagnostics.com (please reply to the newsgroup) |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Error Accessing File - Network Connection May Have Been Lost | mscertified | Setting Up & Running Reports | 4 | April 28th, 2005 04:44 PM |
i read a thread one time that told me | jim sturtz | Fax | 14 | January 24th, 2005 11:11 PM |
File Not Found error when opening network database with multiple u | Dan | General Discussion | 0 | January 20th, 2005 07:27 PM |
Publisher 2000, Windows XP Home, file locked across network | Peter Bilyk | Publisher | 5 | July 21st, 2004 06:05 AM |
Continual Error 1321 Trying to Install Office 2003 | Chad Harris | General Discussions | 9 | June 11th, 2004 08:19 AM |