Reliability of using Access over a LAN?

  • Thread starter Thread starter Grant Schenck
  • Start date Start date
G

Grant Schenck

Hello,

I'm looking to build a solution. It is a simple .NET app which will use a
network shared JET database. The database will consist of a single table
with a single field containing a telephony number. There will be 26 clients
each of which will periodically query to see if a specific number is in the
table (once a minute or so.) In addition, they will periodically use Access
or possibly a simple .NET app to add/delete/view the list of numbers. It is
possible that they may have more then one person adding and that the adding
would happen at the same time as client users are doing lookups.

So, my manager came back with this KB article:

http://support.microsoft.com/?scid=kb;en-us;303528

And statements to the effect that Access is unreliable over a LAN. While
the article does refer to some issues, I see them more as a CYA on MS' part
rather then a fundamental condemnation of using JET over a LAN. The
article is by no means cut and dry.

I last used Access about 10 years ago in a similar sized Networked app and
it was fine. My manager is pushing to use MSDE or build our own server on
top of JET. This all seems like an overkill.

So, what in the concensus of JET/Access developers? Is JET fundamentally
flawed when used over a network or is it basicly pretty reliable when used
mainly for reading and with relativly low query rates and with good backup
proceedures.

Thanks!
 
Grant said:
Hello,

I'm looking to build a solution. It is a simple .NET app which will
use a network shared JET database. The database will consist of a
single table with a single field containing a telephony number. There will be
26 clients each of which will periodically query to see
if a specific number is in the table (once a minute or so.) In
addition, they will periodically use Access or possibly a simple .NET
app to add/delete/view the list of numbers. It is possible that they
may have more then one person adding and that the adding would happen
at the same time as client users are doing lookups.
So, my manager came back with this KB article:

http://support.microsoft.com/?scid=kb;en-us;303528

And statements to the effect that Access is unreliable over a LAN. While the
article does refer to some issues, I see them more as a CYA
on MS' part rather then a fundamental condemnation of using JET over
a LAN. The article is by no means cut and dry.

I last used Access about 10 years ago in a similar sized Networked
app and it was fine. My manager is pushing to use MSDE or build our
own server on top of JET. This all seems like an overkill.

So, what in the concensus of JET/Access developers? Is JET
fundamentally flawed when used over a network or is it basicly pretty
reliable when used mainly for reading and with relativly low query
rates and with good backup proceedures.

Thanks!
Click to expand...

It would probably be fine, but given a choice I would use MSDE or SQL Server.
Jet's "sweet spot" is when used with an Access front end and/or on a distributed
desktop app where the installation and setup of a server database engine is
problematic (and overkill).

On a LAN where a SQL Server or MSDE instance is available or can be easily set
up there is no reason not to do so. Particularly with a dot.net app where you
don't have the simplicity that a Jet back end provides to an Access front end.
 
I have 51 concurrent users using an Access/JET data engine through IIS,
Terminal Services, and on the LAN. We almost never have problems. The last
corruption we had was in 2003 and that was due to a bad Dell aircard (WiFi).

The only thing I see in your specifications that might indicate using MSDE
is the small size of each record. Access uses and locks a 4K page of
records. It is possible that editing such a small record could result in a
locking problem if multiple users attempted to lock the same page. With
MSDE, you can use row-level locking and avoid the problem. Other than that,
Access/JET is perfect for what you are doing. I'd try using it first, and
switch if you have a problem. Moving such a small database should take no
more than half an hour, and all your code written for Jet will work on the
MSDE (but not necessarily the other way around).
--
Arvin Meyer, MCP, MVP
Microsoft Access
Free Access downloads
http://www.datastrat.com
http://www.mvps.org/access
 
Back
Top