Access disconnecting from server?

Usually this means that there is a hardware disconnection. I don't remember
what the monitoring procedure is on Novell, as I haven't used it in 7 years,
but you can use perfmon on a Windows server. Maybe your admin will be able
to help set up a packet monitor.
--
Arvin Meyer, MCP, MVP
Microsoft Access
Free Access downloads:
http://www.datastrat.com
http://www.mvps.org/access

"Diane Yocom" wrote in message
...
sorry for the cross-post, decided to post somewhere with a little more
traffic.

I have an Access 97 database sitting on a Novell server. It currently has
about 5 regular users.

For the past two months, the database has been "disconnecting" at random
times. By disconnecting, I mean, we get the following error:

"L:\Path\DB.mdb isn't 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."

We know the path is correct because the users can access the database
initially, it just seems to kick them out (with this error message) at
random times. If they click on OK through the series of messages, it will
put them back to the database application, but they're unable to do
anything
until they close and reopen the database.

The database hasn't changed, so I don't think it's a code issue. We
updated
Jet 4.0 yesterday and it seemed to be working better, but today people are
having problems again. We're starting to wonder if there is a specific
user/machine that is screwing up all the others.

Does anyone have any thoughts on how to go about troubleshooting this?
Diane Y

also check the version number of the Novell clients (see
if they are all the same), then check the Novell site to
see if any specific problems are listed.

(david)

"Diane Yocom" wrote in message
...
sorry for the cross-post, decided to post somewhere with a little more
traffic.

I have an Access 97 database sitting on a Novell server. It currently has
about 5 regular users.

For the past two months, the database has been "disconnecting" at random
times. By disconnecting, I mean, we get the following error:

"L:\Path\DB.mdb isn't 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."

We know the path is correct because the users can access the database
initially, it just seems to kick them out (with this error message) at
random times. If they click on OK through the series of messages, it will
put them back to the database application, but they're unable to do
anything
until they close and reopen the database.

The database hasn't changed, so I don't think it's a code issue. We
updated
Jet 4.0 yesterday and it seemed to be working better, but today people are
having problems again. We're starting to wonder if there is a specific
user/machine that is screwing up all the others.

Does anyone have any thoughts on how to go about troubleshooting this?
Diane Y

"Diane Yocom" wrote:

I have an Access 97 database sitting on a Novell server. It currently has
about 5 regular users.

For the past two months, the database has been "disconnecting" at random
times. By disconnecting, I mean, we get the following error:

"L:\Path\DB.mdb isn't 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."

We know the path is correct because the users can access the database
initially, it just seems to kick them out (with this error message) at
random times. If they click on OK through the series of messages, it will
put them back to the database application, but they're unable to do anything
until they close and reopen the database.

I'm wondering if there was a Novell Server or client software update
about two months ago.

The database hasn't changed, so I don't think it's a code issue. We updated
Jet 4.0 yesterday and it seemed to be working better, but today people are
having problems again.

Access uses Jet 3.5 so updating Jet 4.0 won't make a difference.
Ensure you have Jet 3.5 SP3 installed on all the systems.

We're starting to wonder if there is a specific
user/machine that is screwing up all the others.

Determining the workstation which caused the Microsoft Access MDB
corruption
http://www.granite.ab.ca/access/corr...orkstation.htm

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm