Michael Bahr
jedi at charm.net
Tue Aug 10 12:20:54 CDT 2010
Brad sounds like you are **not** using any configuration control. The questions you were asking fall inline with this type of control. I strongly suggest that you do some research for a plan that outlines your procedures--this is to protect yourself. A CCB is a group of people that control the releases and what work that gets done. There will be a paper trail documenting all this work. There are many SCM's available, one of which MS uses called Visual Source Safe (VSS), or CVS (open source), and others that cost money but are very robust and full of features. Pick your poision. In a nutshell, when a configuration control system is working--it is a respository for projects, you checkout a project, make changes, checkin the project. This increases the revision number. At some point you what to **release** the project and assign a version number. The CCB will authorize you to do so, again documenting all the work. Now that you have a baseline or new official release you can start working on new requirements that the customer wants. Mike... > Mike, > > I have a tab in the Access 2007 application called "Tech" that only > technical people can see. In this tab are a number of "behind the scenes" > features such as the ability to see logs and the ability to see "Version > Info" (Date, description of changes, etc). Nothing fancy but it does come > in handy when we need to see which version of the system is in affect for > our end users. > > I am not familiar with CCB. Is this a component of another software > package? > > Thanks, > Brad > > > -----Original Message----- > From: accessd-bounces at databaseadvisors.com on behalf of Michael Bahr > Sent: Mon 8/9/2010 11:26 AM > To: Access Developers discussion and problem solving > Subject: Re: [AccessD] "Test to Production" Procedures for Access 2007 > application in a small environment > > Brad, I hope you are using some lind of SCM, Software Configuration > Management application so you can keep track of the revisions and > versions. An SCM "plan" is very useful that defines how these processes > are handled through the CCB, Configuration Control Board. > > Mike... > >> 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. > > > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com >