Could not use "C:\BobDev\abc.mdb"; file already in use

[Bob Barnes]

I sent a Front-end to another city to relink to a Server using a different
letter. My city has "S:", while the other city uses "N:".

The User tried to save/ detach the Front-end mdb by a Copy to the Clipboard
(on a wireless connection laptop) and it stayed as an hourglass. He then
tried a Restart.

After the Restart, he did right-click the mdb attachment and saved it to
C:\BobDev.

Our Help Desk and I will try these..Ideas on this, or alternate solutions.
TIA - Bob

We feel we can try these steps..

1 - The "Restart" would not necessarily "clear" the Copy attempt to the
Clipboard.
The Help Desk guy recommends a Cold Boot, wait 30 seconds, and Powerup
again.

2 - If that doesn't work, I can send another Front-end with NO Links to the
\\abc\eng.

3 - I will also enter this in the Microsoft Access Newsgroup to see what
they say.

I'll check w/ you again this afternoon.

Please let me know if you have any questions.

Thank you - bob

 

[Daniel Pineault]

I'm can't seem to understand your post, but 1 thing did catch my eye.

Access should not ever be used over a wireless connection!

 

[Bob Barnes]

Tell us more.

I'm can't seem to understand your post, but 1 thing did catch my eye.

Access should not ever be used over a wireless connection!

 

[Albert D. Kallal]

Tell us more.

Please read carefully the following article of mine, and ESPECIALLY the part
about why a jet file share can corrupt...

You can if you wish start reading at:

"Why a does JET file share corrupt when the connection breaks?"

article link:
http://www.members.shaw.ca/AlbertKallal//Wan/Wans.html

Since wireless connections are subject to tiny breaks in the connection,
you can blow out your mdb file. In a way it is the equivalent of a
transporter failure in star trek, where part of the data don't make back it
to the other end.

The solutions outlined in the above article not only apply to a WAN, but
also equally well apply to when you use a wireless network. Therefore the
article outlines possible solutions for using access in wan ALSO apply to a
wireless network.

 

[Douglas J. Steele]

What more do you need?

Access is extremely sensitive to networking issues. Wireless connections
typically aren't robust enough for Access. You should never use a wireless
connection to connect a front-end to a back-end.

 

[Daniel Pineault]

What else is there to tell? Dont' do it! Ever!!!

For more details read Albert Kallal excellent explanation about LAN/WANs...
found at

http://members.shaw.ca/AlbertKallal/Wan/Wans.html
--
Hope this helps,

Daniel Pineault
If this post was helpful, please rate it by using the vote buttons.

 

[Daniel Pineault]

Also, read

http://groups.google.ca/group/micro...read/thread/2158968fe8dcf77d/71b7694aeba9d256
--
Hope this helps,

Daniel Pineault
If this post was helpful, please rate it by using the vote buttons.

 

[Bob Barnes]

To All..Thank you.

So..in the future..will Access/ wireless technology "allow" using a wireless
connection for Access?

Bob

 

[Steve Schapel]

Access should not ever be used over a wireless connection!

Hmmm... I think the quality of wireless networking has improved
considerably since the time you formed this opinion, Daniel.

 

[Steve Schapel]

Bob,

I have more questions than answers at this stage.

Does the application have built-in procedure to prompt the user for the
location of the backend data file if it can't find it?

Alternatively, does the user have the ability to use the Linked Table
Manager in order to re-direct the links?

Alternatively, are you able to map a folder or USB drive on your system
as N: and put a copy of your backend here, so you can set up the links
for the other user's scenario before sending theit copy of the front-end
mdb?

I really can't see how restarting and cold booting and whatnot is relevant.

 

[Steve Schapel]

Doug and Albert,

I didn't read your comments before posting by reply to Bob. I stand
corrected by your greater experience. However, I must say I have not
experienced the problems you warn about, in the scenario where I have
used wireless.

 

[Douglas J. Steele]

You'll notice the weasel word I used (i.e. typically) <g>

I've heard of cases where it works fine, but I'm not sure I'd want to base
my business on it!

 

[Bob Barnes]

Steve - The interesting thing...I wrote an App for a network guy's Client.
It has been running several months, and I'm pretty sure it's wireless. just
left a msg for him to call me.

Today's App..it has been running non-wirelss for several years. The guy
today had mapped the "N:" ltr, and I was going to have him manually Link. I
have people trained in 9 other Cities linking w/ no problems.

So, after seeing the wireless ad a few ago w/ a guy sitting at the
50-yardline..I'm curious if/ how this can work.

Thank you - Bob

 

[Bob Barnes]

Doug - Trying to verify one of my Apps I subbed for a network guy..IF it's
good, that makes things very interesting.

 

[Bob Barnes]

John - This particular App has only 18,000 records in the largest Table. I
think my Queries are efficient.

The App has been running 6.5 years and Top Mgmt (it's a large Corporation)
solidly believes in it.

Always loving learning more.

Thank you - Bob

 

[John W. Vinson]

John - This particular App has only 18,000 records in the largest Table. I
think my Queries are efficient.

What you should (strongly!!) consider is basing Forms on queries which return
only one record, so that Access doesn't have to pull the entire table over
into the form's recordsource.

 

[Bob Barnes]

The App has been working wireless. He said it's "very doable"..but it is not
a direct connect over wireless. He said he'll explain more later when we're
at that Client.

 

[David W. Fenton]

What you should (strongly!!) consider is basing Forms on queries
which return only one record, so that Access doesn't have to pull
the entire table over into the form's recordsource.

Argh! It won't do that even when you bind a form to a table, unless
you navigate to the end of the table and back again when you open
the form.

 

[David W. Fenton]

Hmmm... I think the quality of wireless networking has improved
considerably since the time you formed this opinion, Daniel.

I know you posted this before reading the other replies, but someone
encountering this thread may not have read those, either.

Access over a *wired* network can corrupt if the wired network
encounters any hiccups. Most wired networks do not, but bad hardware
or software that's misconfigured can cause DISK OR NETWORK ERROR,
which can lead to corruption of data if it occurs during crucial
operations.

Because of the nature of wireless networks, the connection can drop
and come back up instantaneously frequently without the user of most
apps ever knowing about it. But Access (connected to a Jet back end)
is much more sensitive to it that any other application I'm aware
of.

You don't want to take the risk.

If you must deploy on a wireless network, you must use a server back
end.