Splitting a database

[Melissa]

Hi

I have heard that developers "split" their database. Is that necessary to
do? If so, how is it done?
Does that enable you to put the database on the Company's Server so that
more than one computer on the network can access it?

Thank you

Melissa

 

[Arvin Meyer [MVP]]

If you are contemplating multiple users, it is not only necessary, it is
imperative. You run the data tables on a server and a copy of the front-end
on each workstation, linked to the backend on the server.

If you are using a server at all it is useful and faster to split the
database.

 

[John W. Vinson]

Hi

I have heard that developers "split" their database. Is that necessary to
do? If so, how is it done?
Does that enable you to put the database on the Company's Server so that
more than one computer on the network can access it?

As Arvin says... *do it*.

For some details see
http://www.granite.ab.ca/access/splitapp.htm

 

[boblarson]

And another article:
http://members.shaw.ca/AlbertKallal/Articles/split/index.htm

 

[Tom Wickerath]

And yet another article <smile>

Implementing a Successful Multiuser Access/JET Application
http://www.accessmvp.com/TWickerath/articles/multiuser.htm

Happy reading!


Tom Wickerath
Microsoft Access MVP
http://www.accessmvp.com/TWickerath/
http://www.access.qbuilt.com/html/expert_contributors.html
__________________________________________

 

[troy23]

It gives a slight improvement in performance and is best suited when
there are multiple users.

You export your tables only to a new database and put that on your
server.

You then use the remaining database to connect to those tables.

You put a copy of this database on each users PC


For FREE Access ebook and videos click here
http://access-databases.com/ebook