Multi User mdb

mhisma

Registered User.
Local time
Tomorrow, 01:07
Joined
Sep 20, 2007
Messages
28
Dear All,
I have a mdb file, named by AA_DATA which I put it in the shared folder to enable another team member to access it.
The mdb contains form named AA_INPUT to input data to table named AA_TABLE and I created a shortcut ( on the same folder with the mdb) from AA_INPUT so user can directly open the AA_INPUT with one simply click. The other team member didn't install MS Access in their local PC, so to open MS Access application, they install Access runtime in their PC.
What should I do so AA_INPUT can be opened by several user at the same time ? Is splitting the database and copy the front end database to each user's local PC the only way to enable it?
Kindly need the assistance of this forum
 
What should I do so AA_INPUT can be opened by several user at the same time ? Is splitting the database and copy the front end database to each user's local PC the only way to enable it?
Kindly need the assistance of this forum

That's the BEST way to do it, but that depends on how many users you will have. If only a couple it can be done with one file, but you will be safer as far as corruption issues and being able to open and work with the file if you do split it and give each user their own copy of the frontend.

Oh, and if a user is using the runtime you had better make sure you have good error handling and you will need to create custom menus and toolbars as they don't come across.
 
Bob,
thanks for the quick reply,
is there any way to split database with VBA code ( not by wizard ), so the front_end contain only the AA_INPUT form, while the rest ( queries, macros,tables ) are in back_end mdb ?
Kindly need your advice
 
Bob,
thanks for the quick reply,
is there any way to split database with VBA code ( not by wizard ), so the front_end contain only the AA_INPUT form, while the rest ( queries, macros,tables ) are in back_end mdb ?
Kindly need your advice

That is definitely NOT suggested as that defeats the purpose of a split database. A split database should ONLY have tables in the backend.
 
What I like to do is make a copy of the FE and BE and put them both on the network. Then make a Word document with a command button to copy the FE to the users local drive. This way you can send out the Word document to new users. I have an auto update utility I then use to send out updates.
 
would you like to share how to create a word document that enable copying FE to user local drive and also auto update tools? I think that's the safer way, coz i just worry about the reliability of data
 

Users who are viewing this thread

Back
Top Bottom