Revisions and Modifications

[Scott Viney]

Good morning All,

How do you pros keep a tabs on revisions and/modifcations to a database you
have? I have a database that I have built and as I learn new things or need
to make modifcations I would like a way to keep a record of what it was I
did. Lately I havent looked at it for quiet a while and I have to try and
remember.

Any suggestions or best practices would be appreciated.

Scott V

 

[Douglas J. Steele]

I put extensive comments in. Often (usually?) there will be more lines of
comments in a procedure than actual code. If I change the code, I'll
actually leave the original code there, commented out. If I tried something
and it didn't work, I'll often mention that fact in comments as well (Tried
using xxxxx, but it didn't work because of yyyy)

 

[Scott Viney]

Thanks Doug,

I often comment my code, but what about other things like adding things to
forms etc, new fields to tables? Or modifications to reports?

Scott V

 

[Douglas J. Steele]

Adding new controls to fields or changes to reports, I'll often document at
the start of the form's or report's module.

Table changes (or query changes), ah, yes, there's a potential problem. You
can introduce a module strictly to document things like that.