cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Community Tip - If community subscription notifications are filling up your inbox you can set up a daily digest and get all your notifications in a single email. X

Add support for multiple tables in WQS Reports

Add support for multiple tables in WQS Reports

When you are creating reports you can choose from standard library reports like the System Tree Overview report. If you attempt to add anything to the report from another table you get a series of error messages and you have to kill WQS with the task manager.

Example:

1) Create a System Tree Overview report and delete one of the fields in the details pane to make room.

2) Add Availability from the Configurations Table

3) Attempt to create a report

You will see a dialog box telling you that the Microsoft Jet database engine cannot find the input table...

If you click OK you get the same dialog box. If you click it an additional four times you get a new dialog saying that the operation is not allowed when the object is closed. Click this once again and you are back to the first dialog.

This is an infinite loop. According to Sharon Swaney this is normal behaviour because you are selecting and item from another table. The unsuspecting user would be blindsided by this behaviour. You can't tell this is the problem until you kill WQS, restart it and then try to run your report that you just created. It isn't until you go through this that you get a meaningful dialog saying that you have selected from Prediction Parts and System Tree Items.

So here is my suggestion for a product improvement for reporting:

1) Make it possible to tell from the report editor what the source was for the fields already in a report (You can't tell if Quantity for example is from Configurations, Prediction assemblies, Prediction Parts etc from the report designer)

2) Allow any item from any table to be included in a report

3) Fix the infinite loop dialogs so you can get out without using task manager to kill WQS

4) Make the message more informative (Saying that the Microsoft Jet database can't find something should never be seen by a user, the user shouldn't need to know about the underlying implementation of the tables like the Jet database)

1 Comment
PTCModerator
Emeritus
Status changed to: Archived