Need more than 1 user accessing tables

[Newf via AccessMonster.com]

I lost the steps for which you let more than 1 user to access the database. I
know I have to split the database and also make it a MDE file but not sure
what to do first. After that what do I have to place on each users comp. The
backend will be stored on the network and the front end on the users drive.
Correct??? Also how do I have the user just click on the form without opening
ACCESS and when they exit the entire program closes?

Thanks in advance!!

Newf

 

[Barry Gilbert]

You can use the Database Splitter wizard (Tools, Database Utilities, Database
Splitter). This puts the tables into a seperate mbd file that will live on
your server. The tables with then become linked tables withing the client
version. The client version is what you copy to the end-users' PCs. The
wizard does the whole thing for you.

Creating an MDE is not necessary; it will conceivably make your app run a
little faster (maybe) and will keep prying eyes from any code you have. It
does make it a pain, though, if you ever need to debug while at the user's
machine.

To make a form open by default, use the autoexec macro or select the form's
name in Tools, Startup, Display Form/Page. You can also uncheck the
DisplayDatabase Window checkbox to hide this. To close the app when the form
closes, put a macro in the form's OnClose event that fires the Quit action.

Protecting your database from curious or malicious users is a slippery
slope. There are many steps you can take beyond these, depending on how much
risk is involved in a breach and how much work you want to do.

Barry

 

[Newf via AccessMonster.com]

Barry:
So when i split it I have 2 databases - .mdb and be.mdb. So the BE will go on
the server and the original .mdb goes on the users PC. Do I need to delete
the table that are there on the FE?? Also if I need to place on mulitiple
PC's can I copy the FE and place it on their PC's??

Newf

You can use the Database Splitter wizard (Tools, Database Utilities, Database
Splitter). This puts the tables into a seperate mbd file that will live on
your server. The tables with then become linked tables withing the client
version. The client version is what you copy to the end-users' PCs. The
wizard does the whole thing for you.

Creating an MDE is not necessary; it will conceivably make your app run a
little faster (maybe) and will keep prying eyes from any code you have. It
does make it a pain, though, if you ever need to debug while at the user's
machine.

To make a form open by default, use the autoexec macro or select the form's
name in Tools, Startup, Display Form/Page. You can also uncheck the
DisplayDatabase Window checkbox to hide this. To close the app when the form
closes, put a macro in the form's OnClose event that fires the Quit action.

Protecting your database from curious or malicious users is a slippery
slope. There are many steps you can take beyond these, depending on how much
risk is involved in a breach and how much work you want to do.

Barry

I lost the steps for which you let more than 1 user to access the database. I
know I have to split the database and also make it a MDE file but not sure

[quoted text clipped - 6 lines]

Newf

 

[Barry Gilbert]

Barry:
So when i split it I have 2 databases - .mdb and be.mdb. So the BE will go on
the server and the original .mdb goes on the users PC.
Yes.

Do I need to delete
the table that are there on the FE??

The database splitter wizard will take care of that for you.

Also if I need to place on mulitiple
PC's can I copy the FE and place it on their PC's??

Exactly.
One of the challenges of this architecture is how to deploy revisions to the
front end, especially if you have a lot of users. We've made good use of a
freeware app called StartMdb (http://www.granite.ab.ca/access/autofe.htm).

Barry

 

[Newf via AccessMonster.com]

Barry:
Thanks for prompt response. I'll see if it all works..

Newf

 

[Newf via AccessMonster.com]

Barry:
I went ahead and spit the database and placed the BE in a shared folder on
the network. When I go to the FE the tables are still there. Should they be
gone and linked to the BE?? Also another problem was that I copied the FE and
placed into andother PC but an error came up - "Could not lock table...
Already in use.."

Newf