However, I need to continue to add data to the BE
Since everyone else using their Front ends can update, and add data, then
for what reason would you think you can't?
So, yes....all users, including you can continue to add data. You can even
open the back end direct if you want but the whole idea with splitting was
do avoid more then one person in the back end.
Modifying tables structures is a complete different matter. In this case,
you WILL need to ask everyone to exit the application (or scheduling your
changes at a time when everyone is gone home). In this case, for testing,
and safety, I would make a copy of the back end, and then link my
development front end to this copy. That way, you can test deleting code,
and dangerous update code without trashing the production data.
If you modify a table, or add a new table to the "copy" of the back end,
then I simply make notes as to what I changed. I actually use note pad. I do
this so I don't forget what types of modifications I made.
Here is a sample
tblCustoers
added a new field called SalesRep (text 25)
added a new field called CreateDate (date/time field)
So, I make a notes on the above changes. Then, when it is time to deploy the
new next great version to my users, I will find a time when everyone is out
of the production back end. I will open up my notepad...and then implement
the list of modifying one by one (you do this by hand). I then link my new
great front end mdb to the production back end. You then create a mde, and
it is this mde that you distribute to each user (if you been missing any of
these steps, then you you missed how the development cycle works). This is
the standard approach you will use for development.
For reasons of testing your application, you really don't want to test on
the actually production database. So, you link to a copy of data and then
can test with such ease, and peace of mind. You can add, delete, test
without any worry.
