Client/Server Access application

[Guest]

Hello,

I was told that in a Networked environment with multiple users to design an
Access application with 2 mdb files, where 1 goes on the users HD (Client) &
the other goes on the Server & they are Linked.

That this would be better than using only 1 mdb file on the server &
everyone accessing that one.

Why is this better ? Anyone have links to articles explaining why ?

Thank you,
Jeff

 

[Douglas J. Steele]

http://www.granite.ab.ca/access/splitapp/index.htm
http://www.members.shaw.ca/AlbertKallal/Articles/split/index.htm

 

[Guest]

--
carolyn

 

[Guest]

Hi Doug

Thank you, this was exactly what I needed.

Jeff

 

[Guest]

Just a note of clarification, Jeff.
Microsoft Access using the Jet database is not a client server application.
It is actually a file server application.
The difference is that in a client server environment, the database engine
is running on a server and processes the request on the server. So some of
the processing is on the client computer and some is on the server computer.
The client application provides the User Interface, data validation, and data
requests. The server receives the data requests and processes them and
returns the results to the client all. That would be like SQL Sever, Oracle,
DB2, etc.

With Access and Jet, all the processing is done on the client computer. The
mdb (back end) database is just a repository for the data.