Question Access 2003 with multiple users on a shared network

[Funkyaccess]

Hi

I've been asked to develop an access database that multiple users will have access to. It will sit on a shared network. There will at the extreme most be 20 users. Where should I start?

I've heard of splitting the database and let the user have a local front-end though I dont quiet understand how this work or whether it will be nessary.

Sorry if I have posted this in the wrong section.

 

[DCrake]

Suggest you read this ongoing thread

http://www.access-programmers.co.uk/forums/showthread.php?t=180975

David

 

[Funkyaccess]

So each user should have a mdb file(not a shortcut to the main mdb thats sitting on the shared drive) which uses a linked table that sitts on the shared network?

 

[mcclunyboy]

Hey,

basically I got this wrong too but this is what you need to do:

- Build your database
- Split the database
- Provide all users with the .mdb/.accdb which access the _be

 

[Funkyaccess]

Ok, so carry on as I'm doing, then split it.

How do i package this up for easy setup for the end user? This may need to be installed on other branches network.

whats the difference between .mdb/.accdb?

and _be? I take it thats short for back-end. Sorry I'm new to this forum so just try to get to grips with the terms used.

thanks for your reply.

 

[DCrake]

Pre Access 2007 databases had a default extension of mdb, 2007 changed that to accdb. Also _be was a shortened version of Back End.

David

 

[Funkyaccess]

whats an easy way to package up the front-end/back-end for a user to distrubute?

or should I create to separate zip files and tell a superuser to run the one with a back-end and any normal users to extract the other that has the front-end.

Also what about updates to the DB both front/back end? I dont want it to be a night mare trying to update the DB.

 

[mcclunyboy]

well the easiest updates would be a distribution of updated front ends to all users via whichever method you used to distribute to users.

not sure which is the easiest for you to distribute - if you can acces the 20 users PC's consider just copying/pasting onto their machines...then ensure the linked tables are OK. If not zip files are your way forward

 

[Scooterbug]

There are several ways to distribute updated Front Ends. Several of the people here have code for managing version controls. Off the top of my head, Bob Larson has one on his site.

How I do it where I work (less than 10 users), I put the front end in a shared folder and have a batch file on each users computer that copies over the version I put in the shared folder. I've got my users into the habit of updating before they open up the database.