Database Sharing

[mike]

Hi. I have a database that I am the administrator of. The
database is marked for sharing in the Advanced Options
tab. I have a lot of other databases that are linked to
this main database so it's almost always being linked to
at any given moment. The problem is that other people need
to use the main database but are unable to open it if I'm
using another database that is linked to it. Is there a
way around this? Any suggestions would be great! Thanks!

 

[GVaught]

A database that needs to be shared among several users need to be:

1. Split into two databases; the back-end containing only the tables, the
front-end contains the linked tables from the back-end, the queries, forms,
reports, macros, and modules.

2. Place the back-end on a server type machine; this is needed if you have
more than 10 users using the database concurrently. Note: Win2K or XP Pro
only allow 10 users max. Therefore, you need a 'true' server to service more
than 10 users.

3. Place the front-end on each user's machine. This also aides in making
design changes to the front-end as you never 'mess' with the data on the
back-end unless you have to add a new field to your back-end.

4. Ensure the back-end database has all the correct permissions; read,
write, change, execute. This is needed in order for users to write to the
ldb (record locking) file that is generated when a user open the database.

 

[mike]

THANKS! I'll give that a try.

-----Original Message-----
A database that needs to be shared among several users need to be:

1. Split into two databases; the back-end containing only the tables, the
front-end contains the linked tables from the back-end, the queries, forms,
reports, macros, and modules.

2. Place the back-end on a server type machine; this is needed if you have
more than 10 users using the database concurrently. Note: Win2K or XP Pro
only allow 10 users max. Therefore, you need a 'true' server to service more
than 10 users.

3. Place the front-end on each user's machine. This also aides in making
design changes to the front-end as you never 'mess' with the data on the
back-end unless you have to add a new field to your back- end.

4. Ensure the back-end database has all the correct permissions; read,
write, change, execute. This is needed in order for users to write to the
ldb (record locking) file that is generated when a user open the database.





.