The least portable feature of ROWID references is the scope of a ROWID reference and when it changes for each DataServer. To maximize portability, follow these rules:
Always assign values to unique keys before returning the ROWID value of a record. Some DataServers use a unique key to generate the ROWID value.
If you UNDO a DELETE of a record for which you have stored the ROWID value, return the ROWID value again after the UNDO. It might be different after the record is recreated.
If you update a unique key value for a record, return its ROWID again to replace any prior value.
Never expect a record to have the same ROWID value between sessions.
Note that each DataServer uses a different method to generate a ROWID for a table, and sometimes for different tables in the same database. Therefore, never expect ROWID values to be identical, or even compatible, between otherwise duplicate tables from different DataServers.
For more information on ROWID value construction and scope for your DataServer, see your OpenEdge DataServer guide.
Always assign values to unique keys before returning the ROWID value of a record. Some DataServers use a unique key to generate the ROWID value.