Dependencies and Renaming

[SueBK]

I have a monster of a database, over 100 of each element. Now that we're approaching design of this thing being finished (please God) I'm doing some housekeeping. This involves three steps:

1. Making a note in each element's properties as to its purpose.

2. Working out what is actually being used and what is rubbish that no-one remembered to get rid of. I've used the object dependencies for most that, but I've got a heap of queries that have non dependencies that I KNOW are being used in things like DSUMs. Is there are way to see these non-direct dependencies?

3. If possible, renaming some things for consistency. I know that Access now updates forms and reports with new names (I remember when it didn't, that was painful). But will it update the 'hidden' uses (ie the DSUMs and the like)? I don't want to rename a bunch of things only find I've 'broken' the system!

 

[speakers_86]

3. If possible, renaming some things for consistency.

Be careful with that. If you change it on the table level, you would have to fix every query and every line of code that references that field. I've gone through this before, but you are better off trying to plan your db before you start and stay strictly with your naming convention. But who does that, really?

 

[boblarson]

One thing that is a good tool for renaming is the Free V-Tools. It has a tool called Total Deep Search and it has a replace function. However, I don't know if it would catch DLookups,etc.

The other good one is Rick Fisher's Find and Replace (US $37) which we use here at work. It is very extensive on what it will do.

 

[boblarson]

But whatever you do, do it on a COPY and turn Name AutoCorrect OFF before doing any renaming. It is also known as Name AutoCorrupt because of its ability to corrupt things.