How do I document my database design and keep track of structure changes

[Terri58ds]

I want to document my database so I know what tables are used in a particular query and which forms use that query. In this way if I have to change a table or query I know which other objects I need to update.

I also want to track and document the changes I make to the various database objects (not the actual data).

How do you experienced programmers handle this documentation and version control?
I don't have access to any version control software or the funds to buy anything. I thought I saw a webpage where someone used an Access database to do this but I can't find it now and can't figure out what sort of tables to use.

Thanks,

 

[HiTechCoach]

Here is a previous discussion on the topic:

Creating technical documentation for an Access Applicaiton

 

[irish634]

I want to document my database so I know what tables are used in a particular query and which forms use that query. In this way if I have to change a table or query I know which other objects I need to update.

I also want to track and document the changes I make to the various database objects (not the actual data).

How do you experienced programmers handle this documentation and version control?
I don't have access to any version control software or the funds to buy anything. I thought I saw a webpage where someone used an Access database to do this but I can't find it now and can't figure out what sort of tables to use.

Thanks,

Well when I create large databases, I tend to put objects in groups. If you right click on an object in the DB window, you'll see.

For revision control, you can do something simple and create your own "revision table." For revisions, you can use the auto number. I know it doesn't follow software protocol, but it'll help you track your changes.

Another tool I use frequently is Open Project. This helps me keep track of the actual time I spend on a project and such. It's a FREE alternative to Microsoft Project. Info about it can be found here. You can download it here.

I've also used the documenter to help keep track of things as well.

Hope this helps.

 

[Terri58ds]

Thanks so much for the info and links. I've had a quick read two days ago and hope to read in depth this weekwend.

ETA: HiTechCoach's links pointed me to some great info from Crystal. On further reading and linking through, I found a dead simple solution - the Object Dependencies already sitting in Access! I didn't know it existed until today. It was exactly what I wanted for the first part of my question - seeing which object would be affected if I deleted another.

For the second part - documention modifications I make to each form - I generated a list of objects using Crystal's code (select * from MSysObjects), put them in an Access table with date and description fields.

Thanks again,