Please Help. Getting error message: your network access was interrupted. It is a stand alone DB. We are on a network, but this database does not go out and retrieve any information. Thank you in advance for any trouble.
Rob Dazey
Rob Dazey
your network access was interrupted. Stand alone DB.
- Thread starter RobDazey
- Start date
Jeanette Cunningham
AWF VIP
- Local time
- Tomorrow, 09:37
- Joined
- Aug 8, 2010
- Messages
- 245
This happens when the connection between the front end and backend is broken.
Here's an example.
A database is kept on an external hard drive.
The database is opened and works fine until we accidentally bump the external hard drive (there seems to be a loose connection there somewhere).
The bump causes the computer to re-set its connection to the external hard drive and as a consequence the connection between the front end and back end is broken. To fix this we must close the database and open it again.
In your setup, look for the thing that is causing the connection to be broken between the front end and back end of your database.
Here's an example.
A database is kept on an external hard drive.
The database is opened and works fine until we accidentally bump the external hard drive (there seems to be a loose connection there somewhere).
The bump causes the computer to re-set its connection to the external hard drive and as a consequence the connection between the front end and back end is broken. To fix this we must close the database and open it again.
In your setup, look for the thing that is causing the connection to be broken between the front end and back end of your database.
boblarson
Smeghead
- Local time
- Today, 15:37
- Joined
- Jan 12, 2001
- Messages
- 32,040
As you say it is a STAND ALONE database (meaning one file, no backend or frontend but all together) you need to split the database anyway. It will help avoid corruption where you will lose all of your data. The frontend should be on each person's computer and the backend on a file server in a folder where everyone who uses the database has read/write/delete permissions.
And to go with what Jeannette wrote, you could have a bad router, bad cable, whatever which causes the computer running it to lose contact with the database file. Hopefully you are NOT trying to run this over a wireless connection. If you are, you'd be way better off not doing that as that drops connection quite frequently compared to a hard-wired system. Also if you must use a wireless connection, you really do need to split the database and have a frontend and backend with the frontend on each computer. That will help avoid corruption and also if one person loses connection and their frontend corrupts you just replace it and in the meantime everyone else can still be working with it.
And to go with what Jeannette wrote, you could have a bad router, bad cable, whatever which causes the computer running it to lose contact with the database file. Hopefully you are NOT trying to run this over a wireless connection. If you are, you'd be way better off not doing that as that drops connection quite frequently compared to a hard-wired system. Also if you must use a wireless connection, you really do need to split the database and have a frontend and backend with the frontend on each computer. That will help avoid corruption and also if one person loses connection and their frontend corrupts you just replace it and in the meantime everyone else can still be working with it.
Similar threads
