Hi,
I've stumbled onto a odd problem with a Report, or the Report Engine ...
There is an application that runs client-server and uses the Report Engine to print a specific report using a filter.
It works fine in the current circumstances, but the same application produces Dr.Watson messages (GPF on prowin32) at another customer. This also occurs at my current customer in a test environment with almost the same conditions as the other customer.
The odd thing is that thr problem appears to be linked to the report number (each report has a number which the filter uses to print a specific report), but I don't understand why ...
When printing a report with a number greater than 9999 (thus 10000 and higher) the next call to the report engine will cause a Dr.Watson.
The number is used in the report, but has display format that can work with 10 digits.
Does anyone recognize this kind of odd behaviour ? Or does anyone know what the real problem is ?
As for some extra info:
client: WinNT 4, Progress 8.3b
server: unix, Progress 8.3b
(The other customer uses 8.3d)
Application runs continuously (that is: until the Dr.Watson) and cals upon the printrb interface of the Report Engine.
(table interface will produce the same error)
I've stumbled onto a odd problem with a Report, or the Report Engine ...
There is an application that runs client-server and uses the Report Engine to print a specific report using a filter.
It works fine in the current circumstances, but the same application produces Dr.Watson messages (GPF on prowin32) at another customer. This also occurs at my current customer in a test environment with almost the same conditions as the other customer.
The odd thing is that thr problem appears to be linked to the report number (each report has a number which the filter uses to print a specific report), but I don't understand why ...
When printing a report with a number greater than 9999 (thus 10000 and higher) the next call to the report engine will cause a Dr.Watson.
The number is used in the report, but has display format that can work with 10 digits.
Does anyone recognize this kind of odd behaviour ? Or does anyone know what the real problem is ?
As for some extra info:
client: WinNT 4, Progress 8.3b
server: unix, Progress 8.3b
(The other customer uses 8.3d)
Application runs continuously (that is: until the Dr.Watson) and cals upon the printrb interface of the Report Engine.
(table interface will produce the same error)