Kbase P7637: Is it possible to use the Progress EXTENT 4GL syntax with MS SQL DataServer?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
9/30/2008 |
|
Status: Verified
GOAL:
Is it possible to use the Progress EXTENT 4GL syntax with MS SQL DataServer?
GOAL:
Does MS SQL Server Database have the same schema definition for extent fields as the Progress database has?
FACT(s) (Environment):
MS SQL Server DataServer
FIX:
It is possible to use the 4GL EXTENT syntax with the MS SQL DataServer but it is important to realize that the implementation of array fields is different in the SQL Server Database than in the Progress database.
When a SQL-script is generated by the ProToMSS utility, every element of the array (extent) will be created as an individual field.
For example: the salesrep file in the sports database has a field called month-quota which is an Extent field with 12 extents. The SQL script generated for this table will contain 12 fields with names of:
salesrep.month_quota##1
salesrep.month_quota##2
salesrep.month_quota##3
:
salesrep.month_quota##12
There will be one field for each element of the array.
The DataServer can access the proper data from these fields when the 4GL code uses month-quota[#] syntax by using the element number to access the proper field in the SQL Server database.
The naming convention is very important for this functionality. If you wish to implement this feature in an existing file in your SQL Server database then follow the instructions in Chapter 5 "Adding 4GL Extented Support - Modifying Tables to Support Arrays" in the MS SQL Server DataServer Guide.