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

[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.