I may have created a monster, but for now it is working. However, I need to make what should be a small addition to it and realize how adding one simple field creates a cascade in that I now have to account for all of the places where this addition will have an impact (meaning Tables, Queries, Reports and some VBA code). The main thing that comes to mind is in the Reports, and the Queries that are the foundation of the Reports. I have a lot of them (Queries and Reports).
The problem is there are many possible combinations that need to be "reported" on so I created a Query/Report for each possibility. Then, all the user has to do is click on the button for the Report they want. What this all brings up is my wondering if I've gone about this in an inefficient way.
As I was creating them it didn't occur to me that it might not be the way to do it. Now that I have to go back to add in the new request I realize that I have a lot of places to look to see if I need to make a change to account for this new request. I have at least 75 Queries and associated Reports in order to account for all of the possibilities. So the question is, is it unusual to have lots of Queries and Reports? If not, then I'm set and that's just the way things have to be done. If it is unusual, then do you have any suggestions on how I go about re-thinking the way I'm doing things? That might be difficult without knowing something about "all of the possibilities" so I'd gladly provide some info if that helps.
Probably not the typical kind of question....
__._,_.___
Posted by: Jerry Mathers <jerrymathersasthebeav@yahoo.com>
| Reply via web post | • | Reply to sender | • | Reply to group | • | Start a New Topic | • | Messages in this topic (1) |
.
__,_._,___
Tidak ada komentar:
Posting Komentar