Use Access Database For a Distributed Application

[Guest]

Hi ,
I'm using Access 2003 with Windows XP and I'm developing a distributed
system in Visual Basic 2005 , which will be accessed by many users at the
same time. My requirement is to use MS-Access as the back end for my
application. Currently I'm able to use it as a desktop application with the
database connectivity , but I want it to be used by all instances of my
application which is running in different computers in the same network.

My thought for the above requirement is to have the same database in a
network drive and Can I access the same through network OR Is there any other
good solution for this ?? Kindly comment on whichever would the optimal
solution for this.

Thanks In Advance,
Lokesh

 

[Guest]

Hi Lokesh

Check out this site,

http://www.granite.ab.ca/access/splitapp/

Good luck with your project.

 

[Larry Linson]

I'm using Access 2003 with Windows XP and I'm developing a distributed
system in Visual Basic 2005 , which will be accessed by many users at the
same time. My requirement is to use MS-Access as the back end for my
application. Currently I'm able to use it as a desktop application with
the
database connectivity , but I want it to be used by all instances of my
application which is running in different computers in the same network.

My thought for the above requirement is to have the same database in a
network drive and Can I access the same through network OR Is there any
other
good solution for this ?? Kindly comment on whichever would the optimal
solution for this.

Internet connections are not sufficiently fast for applications to use a Jet
database (yes, even Microsoft miscalls them Access DB) as a back end, which
also applies to most WANs, even ones that don't use the Internet. LANs are,
generally, fast enough to support a modest number of concurrent users
(30 -70 is not uncommon, 100+ if all factors are near perfect) with a Jet DB
back end.

If you have, or grow to have, more users, it is not a really onerous chore
to upscale to a server DB on the back end, but will take some careful
re-examination of your design. It will be even easier, I suspect, because
you'll be using ADO.NET to access both the Jet DB and the SQL Server (or
other) DB.

Larry Linson
Microsoft Access MVP