Hi all.
We run Actuate 7 from within our EAM (formally MLS) application using the server and the ActiveX control. We are using Progress 91D. The Actuate reports connect to the database using the Progress database connection class. We currently have this issue that we can't find a solution to.
The first time the report runs within our application EAM, decimal placement is correct (ex., 1.00). The second and all subsequent times, the decimal moves 2 places (ex., 100.00). The issue has been reported with Actuate ActiveX as well as Report Server. Issue is easily duplicated in non-USA codepage 1250 environments. Issue cannot be duplicated in USA environments where the application is set up to use codepage 1250.
Upgrading now is not an acceptable solution for us, so we need to come up with an actual fix. We have tried so many things, but no luck so far.
Any suggestions?
Any help is highly appreciated.
TIA.
Sirseh
We run Actuate 7 from within our EAM (formally MLS) application using the server and the ActiveX control. We are using Progress 91D. The Actuate reports connect to the database using the Progress database connection class. We currently have this issue that we can't find a solution to.
The first time the report runs within our application EAM, decimal placement is correct (ex., 1.00). The second and all subsequent times, the decimal moves 2 places (ex., 100.00). The issue has been reported with Actuate ActiveX as well as Report Server. Issue is easily duplicated in non-USA codepage 1250 environments. Issue cannot be duplicated in USA environments where the application is set up to use codepage 1250.
Upgrading now is not an acceptable solution for us, so we need to come up with an actual fix. We have tried so many things, but no luck so far.
Any suggestions?
Any help is highly appreciated.
TIA.
Sirseh