Sharing an Access Database with Co-workers

[KMan]

What is the best way to share a database with co-workers (4 or 5 people). I have put it onto a shared network drive so they can access it, but is it possible to allow all of us to access it at once? Right now only one person can access it and edit it at the same time. When someone else tries to access it, it says that it is locked by admin. They can read it, but they can't use it at the same time? Are there any ways to allow a few people to use and edit the database at the same time? No access to Sharepoint or web storage.

[ranman256]

be sure to split the database. The backend tables go on the server, and each user gets a copy of the front end.
all can use it.

[CJ_London]

Right now only one person can access it and edit it at the same time

sounds like you are talking about editing objects (tables, forms etc) as opposed to editing data in those tables. If so, this is not possible. As Ranman suggests, each user has their own front end which if you want to allow them to change forms, reports, queries etc they can do tho' I suspect it will be an administrative nightmare. The backend tables (design) can only be edited when there is only one user on the system.

[KMan]

I've already split the database, what's the best way to distribute the front end?

[KMan]

Ajax, what do you think is the best way to share database without being an administrative nightmare?

[CJ_London]

best way depends on your requirements - typically front end/back end. back end contains tables and relationships only and is located on a shared drive (ideally with a short path, don't bury it 10 folders down), front end contains everything else - ideally as a .accde so users cannot change form design etc. and users run a copy which is located on each users machine.

Where you do not have a designated developer, one user is typically designated 'front end designer' and owns all changes to the db and the master copy. As and when updates to the front end are made, the new file is distributed to the users.

Methods of distribution vary from simply emailing a copy to each user to automated routines which check for current versions etc. Google 'distributing access front ends' or similar to find a method which works for you. It is also important to ensure the back end is backed up on a regular basis - your IT dept may be doing this for you or you may prefer to make an archive copy

It is important that users do not share the front end - that way lies increased chances of corruption. Again you can have routines to check where the front end file is located when opened - if on a network, then it is forced to close - usually with a message along the lines of 'File must be located on your machine'.

[redekopp]

I've already split the database, what's the best way to distribute the front end?

We do this at mostly all of our clients. You literally just copy the front end from the server onto the desktop of the user. And if you ever make front end changes make sure you do it on the server copy and get everyone to re-copy down. That is the simplest way. Maybe add a version number on your home screen of the database so people know if they got the new version or not.

[ranman256]

email a copy to each user.