Is there an add on that helps manage query lists

[jeep2001]

One of my tasks is building and running a lot of queries.
I do this against a db2 database. Often, I find that in developing the final list I have built numerous queries,
and after a while this becomes unwieldy. Is there an add on that would help in storing the queries in a logical manner. I have used the groups a bit and they help.

 

[MajP]

There is probably an add in out there. I just downloaded an free "Access Developers" add-in, but I never even looked at it. Let me take a look to see what is in there. I always figured that Access would eventually come up with a robust file structure view to organize tables, queries, and reports. Do not know about 2003 since I have not used it. Maybe there is something in there.

So I built my own. Using the "Sys" tables, and linking to some other tables, I built forms with tree view controls to organize these things. I put utility in there to click on a table or query and list the field names, variable type without opening the table/query. Similar utility for reports and forms.

 

[MichaelRed]

A way to at least get started is to use the built in "Groups" on the database window/form. Create a new "Group" for each of the functional sets of objects. A nice feature of this is that it need not be restricted to a single object type (e.g. Query), so you can use a group to indicate all the objects required to support some end point functional (User) object. e.g. if you develop a complex report which requires a number of tables and queries, all of them can be listed in your group for that report. Another report can have it's own group, so each function is easily seen and all components required for that function are known.

The bad news is that, kile a lot of Ms. A. the feature only works as well as the individuals self-discipline. There is no automatic way of having the various objects apending themselves to these groups. A dependancy walker function might be able to be adapted to get reasonably close, starting with just the forms and reports collections, but that would (logically) require / expect some method (naming conventions anyone?)of excluding sub-forms and sub-reports from the groups.



MichaelRed