Error accessing file. Network connection lost..... 1

[Darrylles]

Hi,

I am constantly getting this error message after copying and pasting a form to a new form name (to edit and change it in order for it to retain some of it's original functionality - and add to it).

'Error accessing file. Network Connection may have been lost.'

This happens on the works network - but most worryingly on my non-networked home pc.

The solution is: "Copy all code within the form and module(s) and save it, create new database app, import all objects - re-paste the code".

This takes ages, but solves it - UNTIL I copy a form that has most of the functionality that I want in a new form.

I've done it 3 times already - and i'm now getting sick of this unprofessional MS Access dev. tool.

I'm on XP with Office XP.

MS Access has always had an unfair reputation of being a database for secretaries, but it is has finally achieved that previously unfair reputation.

Anyone out there that knows WHY this happens?

There is a MS knowledge-base 'solution' (it's included above), but this is not a solution - it's a reason to go to another db app. dev. tool.
It is ludicrous that you have to spend 50% of development time on rectifying a tools inadquacies.(50% is quite lenient).

Anyone know how to avoid this or solve it without recreating the whole application?

Any links to Microsoft would also help - although they will no-doubt rest on their laurels and give me the finger.

I'm sure that others will start having this prob. Hope I can get to bottom of it.

Kind Regards,

Darrylle







"Never argue with an idiot, he'll bring you down to his level - then beat you with experience." darrylles@totalise.co.uk

 

[hermanlaksko]

Hi Darrylle
I have seen this problem on Access XP and have used the following approch.
Open my app in A2K and compiled the database there...... I know you may not have A2K, but it did hlp me and sloved the problem.
Did you try to compile it in A-XP.
I have learned, over the years, that from time to time one has to import all objects into a new database container in order to get things to work correctly, not as often as you discribe but still, thurs I have developed a function that takes care of all the standard setup og the database (front-end) that I need, this function is called during the start of the program, so "restarting" a program in access is relatively simple.

I have written a FAQ on this subject (creating you own copyright) - you can find it via my username.
Let me know how it works out and I shall help you along the way.


Herman

They say that crime doesn't pay... does that mean my job is a crime?

 

[cuok]

Hi friends!

i think here your solution(?):

http://support.microsoft.com/default.aspx?scid=kb;en-us;304548&Product=acc

CUOK

 

[Darrylles]

Hi,

Thanks Herm - will try that approach.
Cuok - that's the solution I described earlier (very long-winded).

Thank you both.

Regards,

Darrylle

"Never argue with an idiot, he'll bring you down to his level - then beat you with experience." darrylles@totalise.co.uk

 

[danvlas]

Re-create that darn form from scratch, then compile after every line of code (or often enough to give you an idea of where the bug occurs).

It has nothing to do with the network...I think it's related to the separation of VB code from the application.

Access 2000 has the same problem, while Access 97 has NEVER shown such a behaviour.

FYI, I always get this message when I import a form or report that has code behind it.

My solution: before importing, I copy the code to a txt file, then delete it from the form, then import the form and then paste the code...
And immediately compile the project and back it up.

Never been able to properly recover from that darn error unless I followed that exact procedure.

Some times the /decompile works, sometimes it doesn't.

Good luck,




Daniel Vlas
Systems Consultant

http://www.geocities.com/danvlas/AutoMail.html

 

[MakeItSo]

See my FAQ faq705-4683

As Daniel said, the error is caused by importing forms/reports containing code.
Often, you will not be able to get rid of the problem without creating a new db and re-importing the objects.

There is some code, that will cycle through all forms and automatically save the code to a txt file.

Regards,
Andy

Andreas Galambos
EDP / Technical Support Specialist
(andreas.galambos@bowneglobal.de)
HP:

http://www.andygalambos.de

 

[Darrylles]

Thanks MakeIt,

Have just tried to copy and paste your 'automatic code text file creator' into my app. module (after just completing the mammoth task of copying and pasting, copying and pasting, copying and pasting into a new, clean
database) and got - you guessed it.....

'Error accessing file. Network Connection may have been lost.'

This is getting ridiculous.

It seems that I've missed something this time in the 'cut n paste' saga and imported a form with the original code in it - #@{']#~ !!!

What I would like, is for Microsoft to find the reason for this massive 'bug' in their software.

This is now happening regularly - even after copying everything across to a new db, and then say adding a brand new form. Initially - it's ok - then wham!
It seems that some little snippet of code is creating this problem - if only I could get a definitive answer.

I think that I'm going to have to delete or not transfer the latest forms that have been created - one by one - from the last form backwards - until I don't get the problem - this is perhaps weeks of work to get back to
a situation where I can develop instead of bug-fix.

Gates has a lot to answer for.

Sorry MakeIt - thnx for the code - I'm sure it'll work fine - and save me heaps of time once I can get it into my app. (See ya in 2005 - lol)

Kind regards,

Darrylle








"Never argue with an idiot, he'll bring you down to his level - then beat you with experience." darrylles@totalise.co.uk

 

[cuok]

Hi friends,

is your MS ACCESS veresion updated to SP-3?

TRY DO IT IF NOT.

maybe somthing happens when u copied copying forms from 1 version to other

CUOK

 

[bondcat]

Hi all,

I just tried to post this and the bloody thing disappeared! Sorry if it shows up x2.

We have been having this same problem at our office for a number of months now. I thought it had something to do with running Access 2K and Access 97 on the same PC (a necessary evil until our users can be upgraded.). The work around suggested by MS is completely ridiculous as far as I'm concerned. However, based on their suggestion (care of CUOK) I thought I would look into the VBE6.DLL angle...

We have one PC that can import forms no problem in Access 2K, this PC has Win2K [red]SP2[/red] (as opposed to the rest of us with SP3). I checked the versions of the following files to find that this one PC had LOWER versions than the rest of us: VBE6.DLL (Ver. 6.0.89.67), VBE6EXT.OLB (Ver. 6.0.86.67), VBE6INTL.DLL (Ver. 6.0.86.67). I did a test to replace these DLLs on my PC with the lower versions, and lo and behold the problem is fixed!

I don't know if there are any ramifications of downgrading these DLLs. So far I haven't found any problems, but I'm going to test it out a bit more before I get my collegues to do it... If anyone can think of any reason this shouldn't work???

Good Luck,

Catherine

 

[MakeItSo]

Not sure if this wasn't just an incident. i have encountered the effect on various machines with/without SP, with/without complete Visual Basic installed (possible dll clash? - nope).
But this sure is an interesting approach. Star for you Catherine and...

...Please post here, if you find out anything - I'd be most curious!

P.S: If this works - it'll be worth a giant FAQ! ;-)

 

[bondcat]

Hi all,

I've been working for the past 3 days with the downgraded DLLs and nothing seems to have been affected other than my import problem being fixed... I'm getting my collegues to do the same to avoid more corrupted DBs.

Cheers!

Catherine