SQR Porting from 2.26a to 4.0

["V.SHANKAR." <shankar@GIASMD01.VSNL.NET.IN>]

We are looking at a project that refers to a simultaneous migration
from Sybase 4.9 to 11, and SQR 2.26a to SQR 4.0.

Our New Jersey location is running SQR reports under SQR 2.26a of a Sybase
4.9 database on a Solaris Server. We in India are specifically concerned
with migrating a suite of SQR reports generated under SQR 2.26a with
embedded Sybase 4.9 SQL to work under the new environment. (Sybase 11, SQR
4.0)

Since this is a one time exercise, we do not wish to replicate the Solaris
setup in India; instead, since we already have Sybase 11 running on
Windows NT 4.0 on an Intel pentium platform, we wish to use SQR Workbench
for Windows connected to SQR server 4.0 for Windows NT running on the same
server as Sybase 11.

1. Are we correct in assuming that SQR source code transferred from New
Jersey (SQRv2.26, Sybase 4.9) will run fully or partially on the NT setup
(SQR 4.0, Sybase 11)?

2. I understand that the Sybase specific embedded SQL may have to be
changed, and that is in fact the objective of the exercise; but will the
SQR report code run unaltered (apart from version incompatibilities) on
SQR Workbench?

3. Since there is hardly any mail on SQR 4.0 issues, is 4.0 a stable and
tested version, and what are the migration issues between 2.26 and 4.0?

4. Finally, would SQR users recommend the approach being considered by us
as reasonable to effect the migration? Are there any compatibility issues
between SQR report code with embedded SQL generated using SQR Windows
Workbench and SQR for Solaris? What about printer commands porting?

Shankar