Brad Marks
BradM at blackforestltd.com
Tue Aug 10 09:03:10 CDT 2010
Dan, Thanks for the help. I appreciate it. I like your idea of the "Review" system. I plan to experiment with this concept. Thanks again, Brad -----Original Message----- From: accessd-bounces at databaseadvisors.com on behalf of Dan Waters Sent: Mon 8/9/2010 9:43 AM To: 'Access Developers discussion and problem solving' Subject: Re: [AccessD] "Test to Production" Procedures for Access2007application in a small environment Hi Brad, I would add that you need a 'roll-back' copy of the production file. Create a folder named PROD Archive. Each time you want to update, first create a folder within PROD Archive that is named IAW today's date. Then copy the PROD file(s) you are updating to that folder. Then, make the copy from TEST to PROD. With this you can quickly roll back to PROD if you need to. Another thing I've found that's helpful is to have a Review system. If you're working on a longer term improvement, you and your primary contact(s) can use that as a 'see if this is what you want' environment. At one of my customers, we frequently use their ATT Connect on-line meeting software to go through issues and improvements - saves me half a day and a 60 mile round trip! HTH, Dan -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Brad Marks Sent: Monday, August 09, 2010 9:19 AM To: accessd at databaseadvisors.com Subject: [AccessD] "Test to Production" Procedures for Access 2007application in a small environment All, I am in the process of establishing procedures for promoting changes from our Development (TEST) environment to our Production environment. The Access 2007 application uses data from a SQL Server database. There are no local tables. The application is made available to the end-users as an .ACCDR file. I have one folder on the server for TEST and a second folder for PROD. Here the steps that I am currently using. Changes to the Access 2007 application are made and tested in the TEST folder (ACCDB file). Decompile ACCDB Compile ACCDB VBA code / Save it Compact and Repair ACCDB / Save it Run a Utility to Copy the ACCDB file in the TEST folder to the ACCDR file in the PROD folder. I am curious if these steps are similar to the steps that others use and I am curious if I am overlooking anything. Thanks, Brad -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.