This is a new segment we are going to do to get feedback from the blog readers about how you use the product. Today we are interested in how databases are deployed. An Access developer wants to test or preview changes to an app before they are seen by users. An Access developer wants to move an application from one location to another location. An Access developer wants to take an application offline while changes are made. How do you accomplish these things? Before joined the Access team I ran an access development company and here is how we did things as an example to get your started. Test or preview changes to an app before they are seen by users This applies to Split Front-End/Back-end ACCDB’s as well as Split Front-End/Back-end ACCDB/SQL both of which we used. We used to have a developer folder on a network share that would have a master copy of the FE database. We would make changes to that file,
Microsoft Office Ultimate 2007, then roll them out using a .bat file or an EXE on the users desktop that would check to see if their copy was older than the master copy and update it on boot. Simple Updates (No Data or Schema Changes) This would be simple things like re-arranging a form, adding a field to a report. Backup Developer FE Database Open Developer FE database and make changes Manually test changes Rollout update Advanced Update (No Data or Schema Changes) This would be when we wanted to make bigger changes,
microsoft Office 2010 keygen, like how the approval logic worked for a process. Backup Developer FE Database Backup BE Database Open Developer FE database and reconnect the tables to the backed up database Make changes Manually test changes Reconnect Developer FE database back to the main BE database Manually rollout a copy to user(s) and have them test it. Rollout Update Advanced Update with Data & Schema Changes This would be when the updates required we change or add schema and often run some action queries to fix up data. Adding a new section to the databases for example. Backup Developer FE Database Backup BE Database Open Developer FE database and reconnect the tables to the backed up database Make changes to the Developer FE and the BE tables Manually test changes Manually rollout a copy to user(s) and have them test it. Kick all the users out of the database (we would walk around the office, or send an email) Backup the BE one more time with the latest data. Manually make the BE table changes Use Action Queries to make and bulk data changes Reconnect Developer FE database back to the main BE database Rollout update Tell everyone to come back in. Move an application from one location to another location. We would backup the SQL database, create a zip with the FE and the BAK file. Then on the new server restore the BAK file and reconnect the FE database. Take an application offline while changes are made. We would tell all the customers to get out of the database,
Office Home And Stude/nt, not ideal I know but for the most part effective. For MDB’s we used a utility that would show you what users where connected to the backend,
Office Professional Plus 2007, for SQL we could see what users were connected as well. Would love to see how you do it, add your comments!!! (Note: if you are writing a lot I recommend doing it word then copy + paste into the comments,
Microsoft Office Pro Plus 2007, that will save you heartache if the comment fails to post)