Kbase P91837: Not getting the proper format for fields in Static SDO after a schema change and getting error (74).
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
18/08/2004 |
|
Status: Unverified
FACT(s) (Environment):
Dynamics 2.1A
SYMPTOM(s):
Not getting the proper format for fields in Static SDO after a schema change and getting error (74).
** Value <value> cannot be displayed using <format>. (74)
** Value 916525 cannot be displayed using >>>9. (74)
Last procedure in the stack trace indicates that the error is generated by TransferRowsFromDB in adm2/query.p.
Did a schema change to set the proper field format in the schema from >>>9 to >>>>>9, then completed an entity import to get the proper format in the Dynamics Repository.
Entity Control and DataFields show the proper format.
The SDO's defined using the fields that were modified are still getting the old formats.
The field was deleted from the SDO and re-added, but it still uses the old format.
A brand new SDO was defined, but it too used the old format.
Occurring in SDO's defined against the temp-tables database as well as tables in main database.
FIX:
Problems is related to the Entity cache.
The first thing to try is to re-start the session.
If that doesn't work, then check if there are files in the ry/clc directory called ent_<tablename>.d. Either delete these, or regenerate a new one for the relevant entity/table.
There's a tool off the Administration/Deployment menu called Generate Client Cache.