We have customers running on different version of a Sybase database, and some reports appear to hang. (The reports were designed and saved against db version 5.0 and the client tries to run it against db version 7.0)
We can solve this by opening the report with the newer database going to the Show SQL Query window and clicking 'Reset'. The report then runs fine.
Is it possible to perform this reset automatically at run-time using the CRADRT? I already have commands to reset the location, although the DSN and server name (and driver for that matter - P2SODBC.DLL) do not change - it is only the database itself (and the odbc driver) that are different. CRADRT may see they are the same and not force a reset....
Any thoughts? Is there another reset or step which may resolve this?
Thanks in advance,
jlester@lester.com
We can solve this by opening the report with the newer database going to the Show SQL Query window and clicking 'Reset'. The report then runs fine.
Is it possible to perform this reset automatically at run-time using the CRADRT? I already have commands to reset the location, although the DSN and server name (and driver for that matter - P2SODBC.DLL) do not change - it is only the database itself (and the odbc driver) that are different. CRADRT may see they are the same and not force a reset....
Any thoughts? Is there another reset or step which may resolve this?
Thanks in advance,
jlester@lester.com