Garret said:
Let me see if I have this straight -
1) After my database is complete (all tables/forms/reports/ect) are
completed, I split the database.
2) Then I use the Front-End one to customize menu bars and whatnot to
create the User Interface I am looking for. The back end one goes in
a network location.
3) I now use this completely modified front-end to make a MDE, which
then is distributed to all my users.
4) What I am left with now is a backend, and .MDEs for all the users,
with a .MBD that sits in a folder somewhere (this is all customized
too, as it was just used to build the .MDEs).
So now where would I go to create/update more forms/reports? I can't
use this .MBD because it is already modified to be in User Interface.
Once more...
You take your existing unsplit file and you split it. You put the data file
on the network and you leave the MDB on your computer. The MDB is a front
end with links to the tables in the back end. It is IDENTICAL to the MDE
files you will give your users except that it has not been converted to an
MDE.
You make ALL design changes to the MDB. This means the creation of queries,
forms, reports, menus, code modules, etc.. When the MDB works exaclty like
you want it to you make MDEs from it and give them to your users.
When additional changes are required you open the MDB, make those changes
and test them. When you are satisfied with the changes you make new MDEs
and you distribute them to your users who replace their old MDEs with the
new ones. I am usually working on changes in my copy of the MDB almost
immediately after distributing new MDEs because my main app is always being
modified.
I don't understand when you say "I can't use this .MBD because it is already
modified to be in User Interface.". The MDB/MDE _is_ the user interface.
If you mean because once you have set the startup properties and disabled
the bypass key, etc. that the MDB is now not usable for further design work
that is simply incorrect.
You either just re-enable the bypass key on the MDB or simply never disable
it on the MDB copy of the file. You can easily create your MDE, set the
startup properties on it, disable the bypass key, and then make more copies
of it to give your users. You would thus never do those final steps to the
MDB copy. Personally I set the startup properties and just use the Shift
key on my development file and I often don't bother with the bypass key
setting. If I do I run that code in my startup routine so holding shift
still prevents it on my development file and if I accidentally let it run it
is easily enough undone with one line of code.