Keeping track of things

[MikeB]

How do you experienced Access gurus do it? I have only a few reports
and a few tables and already I'm having difficulty figuring out which
queries go into which report, which queries are stuff I was testing
out and which ones I can safely delete without breaking a report.

Do you follow some sort of naming convention?

 

[KARL DEWEY]

Why not build a table that list your table-query-form/report information?
Have another table to track changes made in the database (Configuration
Management).
Keep a copy that relfects any change to the database configuration using
date/version in the name.

 

[Larry Daugherty]

Cheat! Embed each query with the Form or Report that uses it. In the
Form/Report's data properties, open the QBE grid and create and test
the query. When you close the query you'll be asked if you want to
save it. Yes. When asked if you want to give it a name and save it
in the Query window, No.

Then clear out your Query window except for possibly a few Action
Queries. Give the Action Queries longish descriptive names. Never
use a query for more than one purpose or you'll find yourself
modifying it for the current purpose and breaking it for the "other"
purpose - which you won't discover until the next time you happen to
be doing the "other" thing.

HTH

 

[George Nicholson]

No hard and fast rules, but *generally*, I tend to name queries that serve
as report, form or combobox recordsources with "qrpt[ReportName]",
"qfrm[FormName]" or "qcbo[ListName]" respectively.

More general queries might get named "qryDev_[Purpose]",
"qryMaint_[Purpose]". If I know its a one-shot, it might get named "x qry.."
or "qtmp" so it becomes easy to spot and is easy pickings for deletion or
reclassification if it proves to have lasting value.

Its a matter of what 1) will keep you sane and 2) simple enough that it
stands a good chance of *also* making some sense to anyone else with half a
brain who might end up working with the project some day when you aren't
around.