ACCESS 2000 and linking databases

[steve i]

Greetings;
I have a project in which the client would like the database shared within an office enviornment, it is networked. My thinking is to create two databases, one with the data tables only and the other with the queries, forms and reports then link them together, by placing the second database on all computers and first remain (data only) left on one computer. Am I correct in steps of development? If so, what is my method of linking?

Thank you,
Steve

[MMcCarthy]

Greetings;
I have a project in which the client would like the database shared within an office enviornment, it is networked. My thinking is to create two databases, one with the data tables only and the other with the queries, forms and reports then link them together, by placing the second database on all computers and first remain (data only) left on one computer. Am I correct in steps of development? If so, what is my method of linking?

Thank you,
Steve

You are more or less correct Steve.

Create one database containing all the data tables. This becomes the backend. Put this database in a network folder accessible to all the users. After the backend is deployed. In the Frontend database link the tables in from the backend using File - Get External Data - Link. If you move the backend after you create the links the path will be broken. Once you have the links created you can copy the frontend to as many users as necessary.

Mary

[steve i]

You are more or less correct Steve.

Create one database containing all the data tables. This becomes the backend. Put this database in a network folder accessible to all the users. After the backend is deployed. In the Frontend database link the tables in from the backend using File - Get External Data - Link. If you move the backend after you create the links the path will be broken. Once you have the links created you can copy the frontend to as many users as necessary.

Mary

Thanks Mary....

[MMcCarthy]

Thanks Mary....

You're welcome.

[NeoPa]

You are more or less correct Steve.

Create one database containing all the data tables. This becomes the backend. Put this database in a network folder accessible to all the users. After the backend is deployed. In the Frontend database link the tables in from the backend using File - Get External Data - Link. If you move the backend after you create the links the path will be broken. Once you have the links created you can copy the frontend to as many users as necessary.

Mary

Further to Mary's response, it is necessary that all the users access the network address in the same way. To explain this I'll give an example. If John's PC sees the network share that the backend database is on as H: and Fred's PC is set up to see it as G:, then you will have problems. It is actually possible to use network UNCs to specify the share directly, so you can get around it if necessary. It is just simpler to use drive letters.
Another point worth mentioning, is that the FrontEnd database (with all your objects defined) can also be shared and doesn't need to be duplicated on each PC, as long as all users have access to it. It does mean you will need to consider multi-user issues in your design, but that would also be true, even if you did duplicate the databases.