Feedback
Did this article resolve your question/issue?

   

Article

Setup library name is not consistent for Connect for ODBC drivers some places its listed with 's' at the end some places without the 's'.

Information

 
TitleSetup library name is not consistent for Connect for ODBC drivers some places its listed with 's' at the end some places without the 's'.
URL NameSetup-library-name-is-not-consistent-for-Connect-for-ODBC-drivers-some-places-its-listed-with-s-at-the-end-some-places-without-the-s
Article Number000164791
EnvironmentProduct: Connect/Connect64 for ODBC
Version: All supported versions
OS: All supported platforms
Database: All supported databases
Application: N/A
Question/Problem Description
Setup library name is not consistent for Connect for ODBC drivers some places its listed with 's' at the end some places without the 's'.
Steps to Reproduce
Clarifying Information
Error Messagenull
Defect Number
Enhancement Number
Cause
Resolution
The separate setup dll with the 's' at the end is provided only for the Cloud framework or client based drivers like casandra, MongoDB etc. For other drivers the driver library can be used as the setup library.
Workaround
Notes
Last Modified Date12/22/2017 5:17 PM
Files
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.