Error Msg:Error Accessing File.Network Connection May Have Been lost 1

[shez]

Error Msg:Error Accessing File.Network Connection May Have Been lost.

Hi,

The above error message is displaying within an access 2000 application. There are definitely no problems with the server and it is only happening between 2 of the screens within the app! I have been developing the app with Access 2003 then changing the objects (to use 2000 objects)as the users have Access 2000 on their machine's! The app has been deployed onto a server where the users are accessing the app. I am considering upgrading the machines to Access 2003 but am not sure if this will resolve the issue....can anyone offer any help on this please??

Thanks...

 

[RoyVidar]

If it is not a network problem, then it is probably corruption.

This faq Corrupt Microsoft Access MDBs FAQ has a lot of info concerning corruption, symptoms and how to deal with it. MakeItSo's FAQ705-4683 also has some recommandations (and a link to the Microsoft page discussing the issue).

During the last years, I've resolved all my code corruption issues using the /decompile option, in stead of importing objects. It's described here Decompile or how to reduce Microsoft Access MDB/MDE size and decrease start-up times

Here's also an option that might provide some results on exporting/importing database objects Thread705-834817.

Roy-Vidar

 

[shez]

Shall I try reverting back to a previous copy?

 

[RoyVidar]

You probably don't know when the first sign of corruption started, so it might very well have started in your last backup. I would try some of the recommandations in my previous reply (that's why I gave them). Start with the /decompile (follow the detailed instructions on the linked page). Then the others, if it doesn't work.

And please don't crosspost (thread705-932005), have a look at faq181-2886 #4 for why (the whole faq is also worth a read)

Roy-Vidar

 

[shez]

Yeah you are right....thanks I will try this....Sorry about the cross posting I wasnt sure If I had the query in the right forum....

 

[ChopinFan]

Shez,

At least two A2K databases here had the same message recently though neither of them had any corruption and the network connection was fine. We discovered that it was a known bug that was fixed via Microsoft's service pack 3. What was happening for us was that, sometimes (but not always), when objects with encapsulated code were imported from a test database, the code did not compile properly and it caused serious issues. You may want to look into this.

Good luck!