Database Sharing

[mbtransport]

I have looked over the thread of database sharing and they all seem to be out of date, so I thought I would start one for the newer software and go from there.

I have created a database and got it all ready to go, now I need to be able to share it across my network. I have seen people just place it on a shared drive and map users to the location, which is fine with me, I just didn't know if there were any better or different ways in which you can share the database allowing multiple users to interact with the database at the same time.

 

[MajP]

DO NOT DO THAT. Sorry to be alarmist. But you are very likely to corrupt your database and be very inefficient. IMO there is only one way to distribute access as multi user.

http://support.microsoft.com/kb/304932

http://www.fmsinc.com/microsoftaccess/databasesplitter/index.html

You can google this but basically.
1) Split the datbase into frontend and backend.
2) The backend contains only the tables, and that goes on the network.
3) All users get the front end. Forms, reports, modules, macros, queries
4) The front ends link to the back end tables

If you need two do updates to the forms and reports it is easy without worrying about the data.

 

[MazeWorX]

Backup the db if you havn't done so

HTH << MaZeWorX >> "I have not failed I have only found ten thousand ways that don't work

 

[mbtransport]

Thanks for y'all's suggestions, of course I split the database as it seems it is the best route right now. One question I did run across was if I wanted to create a new report, do I create the report by changing the backend file or change the front end file and redistribute it?

 

[dhookom]

Creating new forms, reports, queries, and code are almost always done in the front-end. Then distribute this file to users.

Duane
Hook'D on Access
MS Access MVP

 

[addy]

mbtransport

We have many front end / back end access applications and I use some functionality and code which allows for auto updating of users' front end versions.

I've covered it to a certain extent in this thread:

http://www.tek-tips.com/viewthread.cfm?qid=1646138

But if you want any more information and / or advice on how to implement it, please let me know.

It's very, very useful - best piece of functionality we've ever deployed I think for managing this type of scenario.