Still Getting "Error Accessing File. Network Connection May Have Been" After Updating to SP3

  • Thread starter Thread starter Rob G
  • Start date Start date
R

Rob G

Hi,

I've had problems with the above error before and I thought I've taken all
the steps to resolve it. But it seems to once again reared its ugly little
head. My scenario is as follows:

Each user (about 5) has a front-end on their machine, with the back-end on
the network. Also on the network is a "front-end updates" MDB. Any changes I
make there are picked up by each user's local MDB when opened.

Each time they open their local MDB the queries, forms, reports, etc. are
copied to their machine but they now get that same error. They each have the
SP3 update as well.

Any ideas of what can be done?

Thanks so much.

-Rob
 
The bad error referred to in:
http://support.microsoft.com/?id=304548
is resolved by the service packs, so if the service packs have been applied
to *all* machines, the error message probably does refer to a network
problem of some kind.

To help track it down, consider adding a logging routine to your app, so you
create a table entry when users log in, and then log them out when they exit
the app (using the Close event of a hidden form, since there is no
Application Close event). This should help identify the computer that has
the intermittent network issue. The API calls for the computer name and
network user name can be found here:
http://www.mvps.org/access/api/api0009.htm
http://www.mvps.org/access/api/api0008.htm

Not sure if your "front-end update" is contributing to the disconnection.
You might like to compare Tony Toews' Auto FE Updater at:
http://www.granite.ab.ca/access/autofe.htm
 
Allen,

Thank you for the great information. I will pursue some of those other
courses.

Despite having SP3 on my machine, the error still seems to persist even
though I, currently, am the only one making any changes (the database hasn't
been deployed yet). When I updated to SP3, I never got the feeling it was
done correctly, even though my About box says SP3.

After some testing and being quite certain that there is no network problem,
and being able to reproduce this error at will, I am not sure why this bug
still exists on my database.

If SP3 is installed correctly on my system, should this bug disappear or can
it come back if I copy a form that was one corrupt?

Again, thanks for the advice and direction.

-Rob
 
The error should not recur if you have Office 2000 SP3 and JET 4 SP8
installed.

Just in case the database is partially corrupt, compact and then decompile
it. Then create a new (blank) database, and importing everything: File | Get
External | Import.
 
Back
Top