DatabaseDuane
asked on
Networking issues with Access -- Alert when connection lost
I have a small network of 6 computers linked to my desktop (which has the back-end data) for an MS Access database. It is an Access 2010 system. I'm getting some networking glitches that cause the front ends to fail. I'm pretty sure it is a hardware issue.
My question, though, is how to create a form that pops up on the front end apps when there is an error in the network. Currently, we only discover the problem when somebody does a search for a customer and it doesn't show any results.
A few times, the network disruption error "The Network Has Lost Connection..." pops up that causes the front end to fail, but that is not the typical symptom when something goes wrong.
Any ideas on alerts?
My question, though, is how to create a form that pops up on the front end apps when there is an error in the network. Currently, we only discover the problem when somebody does a search for a customer and it doesn't show any results.
A few times, the network disruption error "The Network Has Lost Connection..." pops up that causes the front end to fail, but that is not the typical symptom when something goes wrong.
Any ideas on alerts?
"how to create a form that pops up on the front end apps when there is an error in the network."
Then what?
Shut down the DB?
What about processing uncommitted actions?
...etc
Most tools to do this will sometimes give false results...
Many times when a network connection fails, it keeps retrying until it succeeds... (or times out)
If you "detect" a drop, a user will think that something is "Wrong", but 1 second later (after a Retry/success), everything may be fine...
This is why the ""The Network Has Lost Connection...", ...is inconsistent.
In other cases some types of network traffic passes, and others might fail.
How are you planning on discerning network activity from the DB only...?
I am not a networking Expert, just an Access Expert, so I am looking forward to see what others post...
;-)
JeffCoachman
Then what?
Shut down the DB?
What about processing uncommitted actions?
...etc
Most tools to do this will sometimes give false results...
Many times when a network connection fails, it keeps retrying until it succeeds... (or times out)
If you "detect" a drop, a user will think that something is "Wrong", but 1 second later (after a Retry/success), everything may be fine...
This is why the ""The Network Has Lost Connection...", ...is inconsistent.
In other cases some types of network traffic passes, and others might fail.
How are you planning on discerning network activity from the DB only...?
I am not a networking Expert, just an Access Expert, so I am looking forward to see what others post...
;-)
JeffCoachman
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I realize that this is a multi-faceted question that I have posted and the most important issue at hand is stabilizing the system. Hardwiring the network is job #1, dedicated server is job #2 and then I'll go forward with next next issues.
<Hardwiring the network is job #1,>
Remember, you never mentioned you were trying this on a wireless network in your first post...
Remember, you never mentioned you were trying this on a wireless network in your first post...
But from this:
"My question, though, is how to create a form that pops up on the front end apps when there is an error in the network. Currently, we only discover the problem when somebody does a search for a customer and it doesn't show any results. "
it sounds like you have something else going on. Unless there is an error, you should not be loosing data. My guess is the DB is corrupt.
You should create a new MDB for the back end and import all the tables into it.
Jim.