Make an Access Database multi user

[Webtechie]

I work at a place that has An Access Database. There are five departments.
Each department is using its own version of the same access database. They
use post it notes to add data from department to department.

I want to make it multiuser. In a design to make it multi-user, I am
thinking that I need to:

1) Install and configure our network
2) Install Microsoft SQL Server
3) Create a SQL Server database from the Access Tables
4) Change the application to use the SQL Server database tables
5) Put the application on a network share drive.

Is this the proper way to upscale an Access 2003 application to be available
to multiple users?

Thanks


Tony

 

[Keith Wilby]

I want to make it multiuser. In a design to make it multi-user, I am
thinking that I need to:

1) Install and configure our network
2) Install Microsoft SQL Server
3) Create a SQL Server database from the Access Tables
4) Change the application to use the SQL Server database tables
5) Put the application on a network share drive.

Is this the proper way to upscale an Access 2003 application to be
available
to multiple users?

You don't *need* to upsize to SQL Server, you *can* use a file containing
Access tables. More info here:

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

Keith.
www.keithwilby.co.uk

 

[Maarkr]

How many users in each department? How many total active users? If < 50, you
may get by with splitting the db, putting the backend on the network, and a
common frontend on each user station.

search this site for splitting a db

 

[John W. Vinson]

I work at a place that has An Access Database. There are five departments.
Each department is using its own version of the same access database. They
use post it notes to add data from department to department.

I want to make it multiuser. In a design to make it multi-user, I am
thinking that I need to:

1) Install and configure our network
2) Install Microsoft SQL Server
3) Create a SQL Server database from the Access Tables
4) Change the application to use the SQL Server database tables
5) Put the application on a network share drive.

Is this the proper way to upscale an Access 2003 application to be available
to multiple users?

Well, it's a bit like buying an 18-wheeler semitrailer truck to haul a couple
of bales of hay... when you already have a perfectly capable pickup.

Access is multiuser and network capable right out of the box. Split the
database into a "backend" containing your tables and a "frontend" containing
the forms, reports, and other user interface; give each user a copy of the
frontend all linked to the same backend, and you're good to go.

SQL/Server makes a very good backend, and you wouldn't be "wrong" to do as you
suggest, but it's certainly not essential, and will be a lot more work.

 

[Webtechie]

Thanks everyone. I never heard of splitting the database. I will do some
proper research and compare it to installing SQL Server.

Thanks again.

Tony.

 

[Tony Toews [MVP]]

I work at a place that has An Access Database. There are five departments.
Each department is using its own version of the same access database.

Are those departments on the same LAN and in the same building? Or
are the spread out in different buildings? How stable and fast is the
connection between the buildings?

If it's a WAN environment then either SQL Server or Terminal Server
should be used.

Tony

 

[Webtechie]

Tony,

There are in different buildings. There is not a network now. That is the
first thing I need to do is create a network. So I hope it will be stable
and fast.

I am leaning more toward using SQL Server.

Thanks.

Tony

 

[Tony Toews [MVP]]

There are in different buildings. There is not a network now. That is the
first thing I need to do is create a network. So I hope it will be stable
and fast.

Ahh, ok, then that's a bit or a lot more troublesome.

I am leaning more toward using SQL Server.

Yes, if not on a LAN then SQL Server or Terminal Server is strongly
recommended.

Tony