Splitting Database Questions

  • Thread starter Thread starter Cam
  • Start date Start date
C

Cam

Hello,

I have a secured database and would like to split it into
a front end and back end. I have the following questions:
1) My database will be shared in a network drive. Where is
the optimum place I should put my front end and back end
database? In the network drive or users PC, C drive.
2) When users enter data in the front end with table link
to the back end. Do they need to hit reflesh or append
data to transfer the data from front end to back end? or
does it automatically update the data w/out doing anything?
3) If the front end is copy to the user PC, what happen if
I need to modify or add (table, form, etc.) to the front
end and Back end? How do I update the design and data?
 
Cam said:
Hello,

I have a secured database and would like to split it into
a front end and back end. I have the following questions:
1) My database will be shared in a network drive. Where is
the optimum place I should put my front end and back end
database? In the network drive or users PC, C drive.
Click to expand...

Back end on a server share, front end on each user's local drive.
2) When users enter data in the front end with table link
to the back end. Do they need to hit reflesh or append
data to transfer the data from front end to back end? or
does it automatically update the data w/out doing anything?
Click to expand...

The latter.
3) If the front end is copy to the user PC, what happen if
I need to modify or add (table, form, etc.) to the front
end and Back end? How do I update the design and data?
Click to expand...

You modify a separate copy of the front end and distribute that when you
are finished. Users replace their old copy with the new one you give them.
Many developers use an automated system for this. For changes to the back
end it is pretty much the same as an unsplit app in that you have to kick
all users out and then make your modifications while you have the file
opened exclusively.
 
Just a comment on splitting a secure mdb. Don't use the database splitter,
or your backend mdb will be unsecured. Instead split it manually:

Make a copy of your mdb and put it on the server. Open it and delete all
objects except the tables. Then compact it.

Open your original mdb, and delete the tables/relationships. Then use File,
Get External Data, Link and locate the backend. Select all the tables and
link. Compact the database.

Then distribute the frontend to your users. The mdw can reside in the same
folder as the backend on the server. Give each user a desktop shortcut to
open the database.

"path to msaccess.exe" "path to frontend" /wrkgrp "path to mdw"
 
Back
Top