So I have gone through the database, and I see only a fraction of the tables are used. The biggest question I have is there are a ton of Cable tables
like Cable10E or Cable1H. These tables are all the same as far as I can tell.
View attachment 92225
And only 10E or cable1h are tied to any forms or reports as far as I can tell.
This seems crazy, but it is as if the developer did not know how to make queries so they made separate tables. Then when they wanted to work on a current cable they redesigned all of the forms and reports to point at a specific table. Do you work on one Cable and then archive that data once complete? Or do you need to get to any cable for its data? Currently it looks as if you work on one Cable and then when complete you archive it.
Normally (and I mean everyone) would have a single Cables table with all data for all your cables. Yes it would be long, but not a problem. Then you can add, edit, and report on any Cable. I think that is what this needs.
For the report you show it should be grouped by CableNo. I would likely have a form on the front end to allow you to pick one or more cables to show in the report. As far as I can tell, the way it is designed now is that the whole database can only work on or report on 1 cable no at a time without someone going in there to redesign the forms and reports. By redesign I mean change in design view the data source.