As I stated in another thread, I have to fix and upgrade some databases. Here is my introduction.
So now you have the overview. The one particular database I am starting with has the most potential for future development, but has these atrocious query and table names. It seems like the place to begin. I have name autocorrect turned on, but I am running into problems right away. The biggest table is named "ChkQry1". Yes it is a table. I ran Object dependencies to get a list of all related queries. I then changed it to something like tblCheck, reran the Object Dependencies and only about 2 of 20 queries survived the change over. The rest still are looking for chkQry1. I know I can open the dangling queries and pop the SQL into wordpad, do a find and replace and then pop it back into the query. I'm not sure there is a more practical approach to dealing with this. I anticipate a lot of debugging, especially in the macro that have these odd query names embedded in them. I may be better off building from the ground up. That starting to look like a more attractive option.[The oddest part of this new assignment is the heavy use Access throughout the department, maybe the whole company. These databases are all in versions 2003 and earlier and rely almost universally on macros, which I hate. They are reluctant to go VBA, but that's where I'm going to have to take them if they want much development. Also these databases have been developed by dozens of different users over a dozen years, most of whom never heard of naming conventions. Queries are named with sentences in some cases. Here's one "Delete Qry older than oldest date on stmt NOT CURRENTLY USED", here's another "Match Stmt to Qry FOR AGING export (45+)". Renaming these to something sensible and debugging the macros will not be fun, but there it is.