Revisions and Modifications

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Scott Viney - 20 Dec 2005 14:52 GMT

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

Reply to this Message

Douglas J. Steele - 20 Dec 2005 15:09 GMT

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)

Signature

Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)

> Good morning All,
>
[quoted text clipped - 7 lines]
>
> Scott V

Reply to this Message

Scott Viney - 20 Dec 2005 16:32 GMT

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

>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
[quoted text clipped - 13 lines]
>>
>> Scott V

Reply to this Message

Douglas J. Steele - 20 Dec 2005 20:38 GMT

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.

Signature

Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)

> Thanks Doug,
>
[quoted text clipped - 19 lines]
>>>
>>> Scott V

Reply to this Message