Did this article resolve your question/issue?



Schema holder update fails after an ODBC mismatch warning.


TitleSchema holder update fails after an ODBC mismatch warning.
URL NameSchema-holder-update-fails-after-an-ODBC-mismatch-warning
Article Number000129851
EnvironmentProduct: OpenEdge
Version: 11.7
OS: Windows 2012 R2
Other: DataServer for MS-SQL Server.
Question/Problem Description
Schema holder update fails after an ODBC mismatch warning.

The failure is due to errors (91) and (565).
Steps to Reproduce
Clarifying Information
A new field has been added to the MS-SQL database.
Error MessageThe schema holder was not created with the odbc driver you have connected with.
You may experience problems with this connection.

Schema Holder: p2sqls27.dll
Current driver: SQLSRV32.DLL

Please consider recreating your schema holder using the current ODBC driver.

** No <file-name> record is available. (91)
** FIND FIRST/LAST failed for table _Field . (565)
Defect/Enhancement Number
Unknown a the time of this writing.
Recreated the schema holder.
Last Modified Date3/5/2018 4:14 AM
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.