Access & Wireless Network problem

[Paul Fenton]

I'm sure this is probably a hardware issue rather than Access, but
thought I'd ask here.

In my home office, I've had a wired network for years and develop
split databases here. I recently went wireless (Linksys) and now am
having no end of connectivity problems.

This workstation where I develop sits about 12 feet from the server
and several times a day, while working in the front end/back end
environment, I'll ge the "Disk error..." message. I have to shut down
Access, open Windows Explorer, click on the mapped drive where the
data file resides to open it, then go back to Access and continue
working.

So even though Access can't connect to the server, Windows Explorer
always does.

Any suggestions?


Paul Fenton
(e-mail address removed)

 

[Brian]

I'm sure this is probably a hardware issue rather than Access, but
thought I'd ask here.

In my home office, I've had a wired network for years and develop
split databases here. I recently went wireless (Linksys) and now am
having no end of connectivity problems.

This workstation where I develop sits about 12 feet from the server
and several times a day, while working in the front end/back end
environment, I'll ge the "Disk error..." message. I have to shut down
Access, open Windows Explorer, click on the mapped drive where the
data file resides to open it, then go back to Access and continue
working.

So even though Access can't connect to the server, Windows Explorer
always does.

Any suggestions?


Paul Fenton
(e-mail address removed)

It's only going to take the most momentary glitch to trip Access up. By the
time you've had a look at it with Windows explorer, the glitch is long gone.

I too use a wireless network at home, but I wouldn't dream of running an
Access FE/BE split across it: far too unreliable.

 

[Joseph Meehan]

I'm sure this is probably a hardware issue rather than Access, but
thought I'd ask here.

In my home office, I've had a wired network for years and develop
split databases here. I recently went wireless (Linksys) and now am
having no end of connectivity problems.

This workstation where I develop sits about 12 feet from the server
and several times a day, while working in the front end/back end
environment, I'll ge the "Disk error..." message. I have to shut down
Access, open Windows Explorer, click on the mapped drive where the
data file resides to open it, then go back to Access and continue
working.

So even though Access can't connect to the server, Windows Explorer
always does.

Any suggestions?


Paul Fenton
(e-mail address removed)

Access needs a really reliable clean LAN.

 

[Paul Fenton]

Brian and Joseph, thanks for the responses. That's about what I
figured, but I kind of thought that Access might be able to reconnect
after the disconnect. Guess not.

Paul Fenton

 

[Albert D. Kallal]

Actually, you should avoid the use of mapped drives.

If you use a unc pathname, ms-access likely would re-connect. The fact is
that you are going into the windows explorer (not ms-access) to force the
re-connect.

So, don't use mapped drive...but use unc pathname

\\yourserver\sharefolder\mydata.mdb

And, when you use the linked table manager, navigate to the back end through
network neighborhood...and forget about the mapped drives, as they are
painful.

While the above will likely fix the re-connect problem, the fact that your
network is constantly dis-connecting would STILL have to be solved, else you
are going to corrupt and damage the data file. Often, using a cordless
phone (which of many operate on the same frequently of the wireless) will
cause a very quick temp dis-connect...and then a re-connect occurs