Feedback
Did this article resolve your question/issue?

   

Article

DataDirect for ODBC 8.0 drivers have separate installers, how will the .LIC be aware of all the drivers installed

Information

 
TitleDataDirect for ODBC 8.0 drivers have separate installers, how will the .LIC be aware of all the drivers installed
URL NameDataDirect-for-ODBC-8-0-drivers-have-separate-installers-how-will-the-LIC-be-aware-of-all-the-drivers-installed
Article Number000185486
EnvironmentProduct: Connect/Connect64 for ODBC, Datadirect for ODBC
Version: 8.0
OS: All supported platforms
Database: All supported databases
Application: n/a
Question/Problem Description

DataDirect for ODBC 8.0 drivers have separate installers, how will the .LIC be aware of all the drivers installed.

For .e.g. Apache Spark SQL and MongoDB have different installers and will be installed in separate installation procedures.
Will second installation run atop of the first one be aware of a previously installed driver? 
If Apache Spark SQL is installed first and MongoDB second, will Apache Spark SQL driver still be valid?

Steps to Reproduce
Clarifying Information
Error Message
Defect Number
Enhancement Number
Cause
Resolution

You can use the installer and its respective key in two separate installation procedures.
The second installation run atop of the first one with will be aware of a previously installed driver , if the installation is performed into the same location/directory that was used for the first installation.

For e.g. If you installed Apache Spark first in location : C:\Progress\DataDirect\ODBC80 and then installed MongoDB into the same location C:\Progress\DataDirect\ODBC80 , both Apache Spark SQL and MongoDB drivers will be valid and can be used because the DDODBC.LIC/IVODBC.LIC file will be updated to include the drivers added during subsequent installations.

If the drivers are installed into two separate locations the the .LIC file will not be aware of the other installation and will not be updated.

Workaround
Notes
Last Modified Date6/23/2016 8:30 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.