Kbase 35836: Error# 5363 and the -nochkttnames startup parameter
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/05/1998 |
|
Solution ID: P5836
FACT(s) (Environment):
Progress 9.1x
SYMPTOM(s):
The caller's temp-table parameter does not match to the target temp-table. (5363)
CHANGE:
Upgrade of Progress version from 9.1B or lower to 9.1C or higher.
CAUSE:
Progress changed the way it handles passing temp-tables as parameters.
Until version 9.1C, you could call a subroutine procedure (external, internal or remote) with a temp-table parameter, where the names of the columns in the temp-table in the caller did not match the names of the columns of the temp-table in the called routine.
In version 9.1C, there is now limited checking of the column names. Each column name in the temp-table definition on the calling side, is sought in the temp-table definition on the called side. If the name is not found, it is ignored. If it is found, then both columns with the same name, the one on the calling side, and the one on the called side, must be in the same column position in both tables.
For example, if the third column in the caller's table is cust-phone, and a column in the receiver's table is also called cust-phone, then it must be the third column of the receiver's table as well. If the caller's column name is cust-phone, and the receiver's column name is something like custphone, without the hyphen, it won't matter since there is no attempt to force all names to match. The matching is also case-insensitive.
FIX:
Use the -nochkttnames startup parameter to suppress the new (since 9.1C) limited checking of column names during the passing of temp-table parameters.