Kbase P122700: Client session crashes using add-columns-from and add-like-column
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
08/03/2007 |
|
Status: Unverified
SYMPTOM(s):
Client session crashes using add-columns-from and add-like-column
Using the add-columns-from and add-like-column methods GPF's the session.
Building a dynamic query and browse using the _sysdatatypes system table causes the session to crash.
SYSTEM ERROR: fmprnt - invalid data type. (62)
The stack trace for the crash is:
//=====================================================
PROGRESS stack trace as of Thu Mar 08 11:51:31 2007
//=====================================================
Exception code: E0000003
Fault address: 7C812A5B 01:00011A5B C:\WINDOWS\system32\kernel32.dll
Registers:
EAX:0012F27C
EBX:00000002
ECX:00000001
EDX:7C97C0D8
ESI:00000000
EDI:00000001
CS:EIP:001B:7C812A5B
SS:ESP:0023:0012F278 EBP:0012F2CC
DS:0023 ES:0023 FS:003B GS:0000
Flags:00000246
Call Stack:
Address Frame
7C812A5B 0012F2CC RaiseException+52
008590A4 0000003E dbut_countl+AB4
CAUSE:
The cause of the problem is the "short" data type used for some of the fields in the _sysdatatypes system table.
The short data type is not supported as a valid data type in the 4GL so should not be used. Attempting to copy such a field to create a new one in the Data Dictionary will result in:
Data type must be character, integer, int64, decimal, logical, date, rowid, raw, blob, clob, datetime, or datetime-tz. (11564).
FIX:
If these system tables are to be used in this way, care should be taken to avoid fields defined with "short" as the data type.