"Why does this happen.."
This value is generated by the db engine when the field is added to the physical schema. Since the fields may have been originally added in a different order then the order in which the Schema
Update routine applies them, the values may end up being different.
"... is there any way to prevent it?"
One way to work-around this would be to write a routine to programmatically generate and apply an incremental DF file to the other target databases (the PSC Kbase has some examples of calling
the OE routines) and then call this procedure from the "updateSchema" event hook that fires after the schema has been updated.
You received this notification because you subscribed to the forum. To unsubscribe from only this thread,
post as spam/abuse.