Sunil,
                Please see the discussion below.  This may be related to our problem with some test region data for an admin table.  Remember that in the test region, the RECID for the records were in an opposite order to the data in Production.  This caused inconsistent results in testing.
                Robert Schlatter
 
From: Jeff Ledbetter [mailto:bounce-jeffledbetter@community.progress.com]
Sent: Thursday, April 12, 2018 8:30 AM
To: TP.Roundtable@community.progress.com
Subject: RE: [Technology Partner - Roundtable] Problem with the position number for fields
 
Update from Progress Community
 

Hi.

"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.

View online

 

You received this notification because you subscribed to the forum.  To unsubscribe from only this thread, go here.

Flag this post as spam/abuse.