MEMO
To: Site Technical Group
From: Poobalan Muniandy, Product Support Manager, SMSS Ltd
Date: 1st October 2007
Subject: 7.12 Artena Reports (Crystal)
Kia Ora.
With the recent launch of Artena 7.12 suites, SMSS would like to make aware to all sites that we have detected differences in SQL syntax between Interbase and SQL Server crystal reports while converting Artena Standard reports. SMSS would like to advise to check your crystal reports for these differences.
To give you an idea of what to look in your reports are :
1. Concatenating strings – Interbase uses “|” to concatenate strings while MSSQL uses “+”
e.g. Interbase: SELECT FirstName | LastName from….
MSSQL : SELECT FirstName + LastName from….
2. Aliases – when selecting fields with the same name from two or more tables, Interbase selects the field from the first table by default
e.g. Interbase : Select StudentIDNumber FROM Person, Student…. (where the field StudentIDNumber exists in both the Person and Student tables)
This statement would return the StudentIDNumber from the Person table
MSSQL : Select StudentIDNumber FROM Person, Student…. (where the field StudentIDNumber exists in both the Person and Student tables)
This statement would give an “Ambiguous column name ‘StudentIDNumber’” exception
To correct this you would need to explicitly specify which table the field is from - Select Person .StudentIDNumber FROM Person, Student….
If you are using Interbase procedures as data sources for your reports, then you’d have to convert them to MSSQL Stored procedures which has some other peculiarities with regards to the use of while loops, cursors and parameters. A good way to check if your reports are working is to copy the SQL syntax off the report and try to run it as a query from SQL server.
If you need further information, please feel free to contact the undersigned.
Kind Regards,
Poobalan Muniandy
Product Support Manager
SMSS Ltd
04 -931 1480
|
| 
