Did this article resolve your question/issue?



Different CRC when .df imported having schema-image connected versus disconnected


TitleDifferent CRC when .df imported having schema-image connected versus disconnected
URL NameDifferent-CRC-when-df-imported-having-schema-image-connected-versus-disconnected
Article Number000181132
EnvironmentProduct: OpenEdge
Version: 11.6.3
OS: Windows 64-bit
Other: OE DataServer for MS SQL
Question/Problem Description
CRC different when .df imported having schema-image connected versus disconnected
Steps to Reproduce
Clarifying Information
The same .df when imported against a schema-holder that has a connected schema-image creates the table with a CRC value different from when it is imported against a disconnected schema-image.
Build environments for code compilation do not connect to the SQL Server database, just the schema-holder.
Progress clients executing R-CODES having SQL Server connected will get a CRC error.
Error Message
Defect/Enhancement NumberDefect PSC00354436
It is a defect. There shouldn't be a difference in CRC value for a table loaded from a .df to a connected vs unconnected logical schema. Fields are loaded in the schema holder alphabetically based on the foreign names. However if the .df file has existing logical position (POSITION), then the logical position is honored unless there is any duplicate position, then the field(s) having duplicate positions are given a new POSITIONs.  
Upgrade to OpenEdge 11.7 or later.
Last Modified Date4/5/2017 4:34 PM
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.