Error accessing file message 1

[SmallTime]

Hi all,

I've started gettting an "Error accessing file. Network Connection may have been lost" message when trying going to the VB window or trying to see my forms in design view.

I've tried compact and repaire and also decompiling but no joy. Also I've tried importing into a fresh database but the problem remains.

Other databases seem fine.

Anyone have an ideas whats happening here and how to fix it?

regards

 

[willir]

Well hard to say, but I have run into this issue.

Resolution was...
- Check your references. From VBA window, "Tools" -> "References". Your application needs libraries, but sometimes you may have compatability problems. For example, FSO scripting / Microsoft Scripting has been problematic for me.
- Create a blank database and import all objects from the problematic one.

Before you start, make sure you create a backup.

Richard

 

[SmallTime]

I search some more and found this article.

http://support.microsoft.com/default.aspx?scid=kb;EN-US;304548

It seems this is a recognised problem with a particular version of vbe6.dll. However, their solution seems very painful indeed.

Anyone know of a better, less painful fix?

 

[RoyVidar]

The decompile didn't work?

Suggest having a look at the methods here thread705-834817 (if you're able to access/run any code at all). If it works, it'll save a lot of work.

Note - if you can't run the fully automated routine, try each object:

[tt]application.saveastext acform, "MyForm","C:\myform.txt"[/tt]

In the new application

[tt]application.loadfromtext acform, "MyForm","C:\myform.txt"[/tt]

Roy-Vidar

 

[SmallTime]

Many thanks Roy. I've copied the link for future ref in case things go wrong again.

I was missing office 2000 sp3 and after loading this imported all objects into a new MDB, compiled and then ran compact and repair. Things have become stable again and all's ok now it seems, although it'll take me some time to check the whole app.

Although I had a back-up it was about 2 weeks of work behind. So just in case someone else reads this. MAKE A BACK-UP NOW.

As a thought, it seems this hick-up stems from Microsoft releasing some updated dll's and not taking enough care to check on consequences. Since it was their cock-up I'd have thought they would have been responsible enough to issue a proper fix as well. Or am I just expecting too much?

Kindest regards and thanks again for your good advice and pointer.

 

[SmallTime]

When debugging my old fe to try and the fault I found that parts of the code were missing. Only a few letters at the begining of some of the procedures (seems at random) eg what was showing as 'Private Sub' now showing as 'te sub'. Or in some cases the last few letter are missing at the end of a piece of code.

Also, more worrying I found things like this embedded in various parts.



ExitŽž:?
?9‚rr@MsgBox
;.ÀDescridƒpResuÀRC
°
EndC’95¢9D A*9im stDocBŸAs S9@¤ng…‡
ƒ^OpenAÃɇ*, A
0Šÿ…q\OŒè[Õãó‘xEŒ78¯UNŒEÑ ¿opOŒ 8*‡OŒopaO‹h?O‹O‹2?ÏU£–O‹iþaÎ-´¿º[¿¿ϹÔ¿¦79¿¿÷D¿¦ “/¿#¨3 ÿê/¦$C¿¿¿ÿ¥¥yd¿º[¿¿?Ï¿ÀŒa!)(CþlÀØ$Œ”!³¿SïÜHnµ2'nL³d5

URunMðacroç<q"LÿôOJ[OO
Z<óo"o"54OODO_Áªïg¶k IERHfy Cà™worküerÉ
´
o[?kB0tn_c‘@Yº_m$as@y_o?u_R>eá#%
¿f§¯edý¯wªÏÌç.êbïsé3 Mb¤csòt_gef_g7
sSgÿ4S2 2´?\oh¿‡p\‘ÿß0Ñ+!!Ÿžÿ´##ß ÛÛ Ã_iûá·M6?[hÉÔ=EñŸOÉOÉ0ÊOÉnuKÉÿ|o‰6ÕÉɾ¿?!ÏÊ$=?ÛØg6D?Ï1ŸJ ï^à^™JceÿïIïI! 
_ZZ

Z÷"âFY ñ-D
e]}'ámptsà user²su¸V`ÿ£¡3²$¿°ÙA
4ۤUvwہ
oDpÔoRÝxObj°Æ?
1f…
=)P?!xS.'Wi˜th 5ñ>As#newƒ

Anyone know what it is and how it appeared?

 

[RoyVidar]

Have neither seen nor read about corruption of that kind, it usually occurs within the compiled bits, not the original texutual representation (which is why /decompile often can resolve corruption).

A little warning, though, you don't know how long there's been some corruption going on, you might very well have the beginnings of it in your backup. Take the measures necessary to ensure there are no corruption. On a working db, the methods in the thread I provided, should work, both as a method of having a spare (textual) backup, but also to create a new uncorrupted db.

Perhaps Microsoft would be interested in studying the database?

Roy-Vidar

 

[SmallTime]

Many thanks.

I suspect Microsoft already know about the problem, hence the advice on

http://support.microsoft.com/default.aspx?scid=kb;...

Regards

 

[cjkoontz]

A couple questions of ignorance:

(1) As far as the Microsoft resolution is concerned --
On the File menu, point to Get External Data, and then click Import. Import all tables, queries, forms, reports, data access pages, and macros to the new database.

What if your mdb only has linked tables?

(2) I am trying to open the problem mdb in Access XP, and I get the same error. I'm at the level of XP SP3, and my version of vbe6.dll is not the offending one.

Am I experiencing the "error accessing file" message because the problem mdb is corrupt?

 

[cjkoontz]

It appears that in test with Access XP, you can export the linked table from one db and then import it into another.

http://support.microsoft.com/?kbid=208991