There is not really a good solution to this problem. (at least now, you can
modify code/forms/reports, and not loose all your chances, or have everyone
STOP working on the application). So, the split has tremendous advantages in
terms of a non split system. And, to make changes to the non split system,
you still had to kick everyone out for changes to the table structures.
The way I approach his problem is I make CAREFUL notes. For example, if I
add a date field to customer table, and I call it ExpiryDate, then I make a
little notepad document.
tblCustomers:
add field ExpirtyDate, indexed
add field ActiveCustomer, true/false
And, lets assume I also added a complete new table, in my note pad, I will
write;
tblReminders: new table...import from development back end.....
So, you can see that the list is NOT very complex. As I development, each
new field/table change is written down in this document. When I get back to
the clients site, then I fire up (notepad) to view the above list, schedule
a time when everyone MUST be out of the back end, and then quickly add the 2
new fields to the tblCustoers tables, and then import the new table called
tblRemmbers. At this point, then everyone can go back in...
The tricky part is if you can't be on site. Because the time taken to test
the code that would modify the back end, I find it better to have the
customer email me the back end data...I modify it..and then send it back.
I have on occasions written code in the FE that does modify the BE..but the
work involved is more then the above...