Before posting I checked for Revision and revision control but didn't get the results I needed so here goes.....
I have been unable to find any informtion about how to control/document database revisions.
I have been using a database created specifically for the purpose of documenting changes/enhancements/fixes. This was good enough when I was creating simple applications for my own use. But now I've had to take over management of a multitude of databases following the death of a coworker. All of the databases reside on the network and none were designed as backend/frontend so I had some problems at first with data loss when users corrupted the database(s). My co-worker used to restore from an old version and ask people to re-enter their lost data. I figured there had to be a better way.
So I split a few databases and that is helping. But I've recently been thinking about how to properly manage revisions.
I have a split database and am making enhancements to the front end. After I'm done I want the users to replace their current copy with the new one. But that requires some information. How does the user know they have the latest version? How do I know they have the latest version?
My idea is to create a one field table in back end that contains the current revision. Another one field table resides in the front end. I have a splash screen that opens with the DB that opens hidden but becomes visible if the Back end and Front end revisions do not match. THe screen then asks if the user wants to update. If they answer yes, they receive instructions for deleting their hard drive copy and replacing it with the NEW version from the network. WHen they open the new database for the first time the user is prompted to answer a few questions that set parameters for them. I have different configurations for users to choose depending on their role. Completion of that form sets the Front end revision equal to the back end revision. THe user then does not see either the splash screen or parameter screen again until I change the revision.
I had thought about also maintaining the revison table to show history (perhaps revision, memo and date) and also had more elaborate thoughts about a revision database that would poke the new rev number into my db when I was ready to release.
Am I perhaps being a bit anal about rev control? Is there a better way? Just looking for help. By now I'm sure you've figured out that I have little formal training (6 days at a microsoft cert school) and I'm a little lost.
thanks,
Dave G.
I have been unable to find any informtion about how to control/document database revisions.
I have been using a database created specifically for the purpose of documenting changes/enhancements/fixes. This was good enough when I was creating simple applications for my own use. But now I've had to take over management of a multitude of databases following the death of a coworker. All of the databases reside on the network and none were designed as backend/frontend so I had some problems at first with data loss when users corrupted the database(s). My co-worker used to restore from an old version and ask people to re-enter their lost data. I figured there had to be a better way.
So I split a few databases and that is helping. But I've recently been thinking about how to properly manage revisions.
I have a split database and am making enhancements to the front end. After I'm done I want the users to replace their current copy with the new one. But that requires some information. How does the user know they have the latest version? How do I know they have the latest version?
My idea is to create a one field table in back end that contains the current revision. Another one field table resides in the front end. I have a splash screen that opens with the DB that opens hidden but becomes visible if the Back end and Front end revisions do not match. THe screen then asks if the user wants to update. If they answer yes, they receive instructions for deleting their hard drive copy and replacing it with the NEW version from the network. WHen they open the new database for the first time the user is prompted to answer a few questions that set parameters for them. I have different configurations for users to choose depending on their role. Completion of that form sets the Front end revision equal to the back end revision. THe user then does not see either the splash screen or parameter screen again until I change the revision.
I had thought about also maintaining the revison table to show history (perhaps revision, memo and date) and also had more elaborate thoughts about a revision database that would poke the new rev number into my db when I was ready to release.
Am I perhaps being a bit anal about rev control? Is there a better way? Just looking for help. By now I'm sure you've figured out that I have little formal training (6 days at a microsoft cert school) and I'm a little lost.
thanks,
Dave G.
