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?
DatabaseDuaneAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Jim Dettman (Microsoft MVP/ EE MVE)President / OwnerCommented:
Unless your handling all the record saves your self in code, then you would need to place code in each forms OnError event to trap anything.

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.
0
Jeffrey CoachmanMIS LiasonCommented:
"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
0
Boyd (HiTechCoach) Trimmell, Microsoft Access MVPDesigner and DeveloperCommented:
Are you running  wireless network?  If yes, this is you main issue. You really need to be hardwired. I have yet to see a wireless network not have regular issues.
0
Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

Nick67Commented:
And in some ways, an alert is superfluous.
If you've lost your network connection, Access is going to bomb--and usually spectacularly.
The front-ends usually hang, and sometimes get corrupted.
It is just all-around bad--but you usually know it right away.
"Disk or Network error" popups--zillions of them.

I'd suggest:
A wired connection for all clients
A real server if you can afford one.
A workstation that does nothing else but serve files if you can't.
Good backups of both the front ends and back ends

Because if you have connection issues, something is going to get corrupted sooner or later
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
DatabaseDuaneAuthor Commented:
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.
0
Jeffrey CoachmanMIS LiasonCommented:
<Hardwiring the network is job #1,>
Remember, you never mentioned you were trying this on a wireless network in your first post...
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Access

From novice to tech pro — start learning today.