Kbase P51432: Why does _file._ianum not change after a tablemove is performed?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
26/08/2009 |
|
Status: Verified
GOAL:
Why does _file._ianum not change after a tablemove is performed?
GOAL:
Why does _ianum for a table not change after the table is moved to a new location using the tablemove command?
FACT(s) (Environment):
All Supported Operating Systems
Progress 9.x
OpenEdge 10.x
OpenEdge Category: Database
FIX:
The _File._ianum field contains the storage area number that a table was created in. If a table is moved using the tablemove command the _file._ianum is not updated to reflect the new location. After the table is created the _ianum field is not used again.
This is by design of the Progress Developers.
To determine the area location of a particular table use the _area-number code instead of _ianum. For Example:
FOR EACH _storageobject WHERE _object-type = 1.
FIND _file WHERE _file-num = _object-number.
DISPLAY _file-name _area-number.
END.