Kbase P115942: The windows client gpf after error 52
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
5/10/2006 |
|
Status: Unverified
FACT(s) (Environment):
DataServers
Oracle DataServer
SYMPTOM(s):
The windows client gpf after error 52
SYSTEM ERROR : fmx -- bad data type.(52)
The procore shows both error 52 and 708
Userid is now <name>. (708)
Procore file shows the following:
Date Time [2560]
Progress Recent Message(s):
(52) (708) (708)
SYSTEM ERROR: fmx -- bad data type. (52) Userid is now <name>. (708) Userid is now <name>. (708)
*** 4GL Call Stack ***
...
CHANGE:
User changed foreign position (FOREIGN-POS) of several fields in different tables in the schema holder df file before loading it to the schema holder
CAUSE:
Change of the foreign position without knowing the exact position caused the error 52
FIX:
Follow the steps below to fix the problem:
1. Delete the tables in which the FOREIGN-POS of the field was changed.
2. Use Update/Add table definition tool from the Oracle DataServer utility in the Data Administration to re-pull the tables from the Oracle Database.
3. Use Adjust schema tool from the Oracle DataServer utility in the Data Administration for the selected the tables to reflect the Progress compatible objects.
Note: If the tables from the step 1 are not being identified, create a new schema holder to pull the Oracle database schema to the Progress Schema holder. Then perform the adjust schema (Step 3) for all tables to reflect the Progress compatible objects.