Have a question regarding an Access upgrade that would be coded offsite while the database remains in use.
Hopefully I have explained adequately!
- Database is split into front end and back end - code and data
- It will otherwise be business as usual during coding, form and database upgrades
- Mix of Access 2003 and 2010 clients
After development, I will need to upgrade the Access database front end and back end for the upgrades which will involve minor changes to the database schema as well as new coding and form changes. My question involves how to best integrate this back into the client's workflow (mainly as it related to data integrity since the code is all in the font end).
I know there will need to be provision made for "old data" that now has new fields to reference (will set defaults and populate - or filter from results) but how will it be best to ensure the customer's data remains intact and accurate? Will I need to carefully mirror the database changes made during development when onsite with the customer's "current" data (can be offline for that time) or is there a better way? It seems potentially "troublesome" to use the new table structures and import data from the "live" data set but this is the only other way I can think of.
So, in summary - what is best?
1) Modify database structure to mirror development changes when onsite on existing back end
2) Use new database back end and import all table data when onsite from the previous back end data
3) Hopefully - a better option??
Please advise according to experiences and not (just) a link to an overly long, related article.