Do it when everyone's off. Keep a good backup copy of it before you split it
so you can go back if you run into problems. Go to Tools - Database
Utilities - Database Splitter and it will seperate it into a front end/back
end for you. All your tables will be linked to the back end when you are
done and you will have a seperate database with the same name except that
there is the "-be" added to the name. Play with it and check for problems -
I don't think you will have any. The only thing I do differently is: I
don't include the switchboard (if your using one) table and any lookup tables
in the back end - I keep them in the front end. That way if I change
anything in the switchboard it carries with my frontend. Just my preference.
I especially enjoy the fe/be setup because I often make changes to the front-
end that I post to the server, I have the users hit an icon on their desktops
to copy the newer version down to their desktops with my changes. With the
fe/be you have freedom of doing this without worrying about overwriting your
data. Makes it easier on the developer. The good news is you can always go
back to your backed up version if you have a problem.
If you have any problems with the tables linking, go to Tools - Database
Utilities - Linked Table Manager and relink the tables.
Message posted via AccessMonster.com