Access 97 database error after standby mode

  • Thread starter Thread starter Lord Kelvan
  • Start date Start date
L

Lord Kelvan

I am getting this error sometimes after my computer comes out of
standby mode

path.mdb is not a valid path. make sure that the path name is spelled
correctly and that you are connected to the server on which the file
resides.

it works fine while I am using the computer but if i go away for lunch
then come back after a while this error happens

It happens on other pcs on my network as well.

I have attempted the disabling of the power options on my network card
but this is to no avail.

I am not 100% sure if it is my code or the computer but i am leaning
to the latter.

If anyone has any solutions it would be great.

Regards
Kelvan
 
I am getting this error sometimes after my computer comes out of
standby mode
Click to expand...

I can see how this can be a problem if the PC goes into standby mode.
As soon as the PC has awakened it's going to take a few seconds to
re-establish the network connection. But in the meantime Access
want's to hit the database file immediately.

So the only solution, in my opinion, would be
1) exit the app before leaving your PC for a while
2) ask the IT staff to extend the standby time to, say, 2 hours
3) implement some logic that kicks the users out before the standby
time is encountered. Idle Detect/Inactivity Timeout
http://www.granite.ab.ca/access/idledetecttimeout.htm

Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
For a convenient utility to keep your users FEs and other files
updated see http://www.autofeupdater.com/
 
I can see how this can be a problem if the PC goes into standby mode.
As soon as the PC has awakened it's going to take a few seconds to
re-establish the network connection.   But in the meantime Access
want's to hit the database file immediately.

So the only solution, in my opinion, would be
1) exit the app before leaving your PC for a while
2) ask the IT staff to extend the standby time to, say, 2 hours
3) implement some logic that kicks the users out before the standby
time is encountered.  Idle Detect/Inactivity Timeouthttp://www.granite.ab.ca/access/idledetecttimeout.htm

Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages -http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog -http://msmvps.com/blogs/access/
For a convenient utility to keep your users FEs and other files
  updated seehttp://www.autofeupdater.com/
Click to expand...

i though of this but the problem with this is i need to have a few
systems running in the background to provide alerts in releation to
the data. though on mentioning this i wonder if access will complain
if there is no data and it is just program code.
 
i though of this but the problem with this is i need to have a few
systems running in the background to provide alerts in releation to
the data. though on mentioning this i wonder if access will complain
if there is no data and it is just program code.
Click to expand...

I think Access will still complain. Now this is almost a decade ago
but I watched the network resources of an Access 97 FE linked to an
Access 97 BE. There was a constant 2.5 kpbs stream of data going to
the backend with a spike every 25 or so seconds. Is that still true
in Jet 4.0 or ACE? I don't know.

Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
For a convenient utility to keep your users FEs and other files
updated see http://www.autofeupdater.com/
 
Back
Top