My solution involved existing PRO*COBOL modules compiled into Visual COBOL. and for this we are using 64 bit ODAC drivers provide by Oracle.
Installation of the ODAC drivers have been successful, however when trying to consume the drivers using ADO.NET Connect Editor I endup with dependency on Microsoft .Net framework 3.5 or lower where as the ODAC provider is .Net 4.5 and above and I've selected Framework as 4.0 and above in ADO.Net and the CPU architecture as 64 bit.
It would be great, if some one can point me in the right direction to install and use ODAC 64 bit drivers for my Visual COBOL 64 bit without any dependency on the 32 bit framework or 3.5 framework.
Below are some images from my experience.
Image 1.
Image 2
Image 3
It is currently a requirement of the ADO Connection Editor to have the 32-bit CLR 4 provider installed even if you only intend to create 64-bit connections using the 64-bit ODAC installs. This is due to the fact that the editor itself is 32-bit and in order to query the various providers for their properties to display in the grid it can only use the 32-bit version.
Try installing the 32-bit ODAC system as well and this should work correctly for you.
Thanks
My solution involved existing PRO*COBOL modules compiled into Visual COBOL. and for this we are using 64 bit ODAC drivers provide by Oracle.
Installation of the ODAC drivers have been successful, however when trying to consume the drivers using ADO.NET Connect Editor I endup with dependency on Microsoft .Net framework 3.5 or lower where as the ODAC provider is .Net 4.5 and above and I've selected Framework as 4.0 and above in ADO.Net and the CPU architecture as 64 bit.
It would be great, if some one can point me in the right direction to install and use ODAC 64 bit drivers for my Visual COBOL 64 bit without any dependency on the 32 bit framework or 3.5 framework.
Below are some images from my experience.
Image 1.
Image 2
Image 3
One other thing, If you don't wish to get a warning message about the inability to Save the connection info for older Frameworks like 2.0, 3.0 and 3.5 then select the settings arrow at the top of the editor and under Save uncheck that option for All framework availability combinations.
It is currently a requirement of the ADO Connection Editor to have the 32-bit CLR 4 provider installed even if you only intend to create 64-bit connections using the 64-bit ODAC installs. This is due to the fact that the editor itself is 32-bit and in order to query the various providers for their properties to display in the grid it can only use the 32-bit version.
Try installing the 32-bit ODAC system as well and this should work correctly for you.
Thanks
I am facing same issue. System didn't allow me to install both 32-bit and 64-bit ODAC. Please help
I am facing same issue. System didn't allow me to install both 32-bit and 64-bit ODAC. Please help
Hi,
Can you please provide more detail about the problem you are having? What exactly is happening and what error is being reported?
Hi,
Can you please provide more detail about the problem you are having? What exactly is happening and what error is being reported?
I am trying to create DSN for oracle with ODP.Net provider, but I am getting below error.
I am trying to create DSN for oracle with ODP.Net provider, but I am getting below error.
What Visual COBOL product version are you using?
Are you starting the Connection Editor as Administrator?
If the Oracle ODP provider is installed correctly it should be present in the machine.config file which can be found here:
32-bit: C:\\Windows\\Microsoft.NET\\Framework\\v4.0.30319\\Config
64-bit: C:\\Windows\\Microsoft.NET\\Framework64\\v4.0.30319\\Config
When the driver is installed it should update machine.config so that it contains entries like the following. If it does not contain these entries then the provider was not installed properly and the ADO Connection Editor will not be able to use it:
<section name="oracle.manageddataaccess.client" type="OracleInternal.Common.ODPMSectionHandler, Oracle.ManagedDataAccess, Version=4.122.19.1, Culture=neutral, PublicKeyToken=89b483f429c47342" />
And
<DbProviderFactories>
<add name="ODP.NET, Managed Driver" invariant="Oracle.ManagedDataAccess.Client" description="Oracle Data Provider for .NET, Managed Driver" type="Oracle.ManagedDataAccess.Client.OracleClientFactory, Oracle.ManagedDataAccess, Version=4.122.19.1, Culture=neutral, PublicKeyToken=89b483f429c47342" />
</DbProviderFactories>
Are these entries in your machine.config file?
What Visual COBOL product version are you using?
Are you starting the Connection Editor as Administrator?
If the Oracle ODP provider is installed correctly it should be present in the machine.config file which can be found here:
32-bit: C:\\Windows\\Microsoft.NET\\Framework\\v4.0.30319\\Config
64-bit: C:\\Windows\\Microsoft.NET\\Framework64\\v4.0.30319\\Config
When the driver is installed it should update machine.config so that it contains entries like the following. If it does not contain these entries then the provider was not installed properly and the ADO Connection Editor will not be able to use it:
<section name="oracle.manageddataaccess.client" type="OracleInternal.Common.ODPMSectionHandler, Oracle.ManagedDataAccess, Version=4.122.19.1, Culture=neutral, PublicKeyToken=89b483f429c47342" />
And
<DbProviderFactories>
<add name="ODP.NET, Managed Driver" invariant="Oracle.ManagedDataAccess.Client" description="Oracle Data Provider for .NET, Managed Driver" type="Oracle.ManagedDataAccess.Client.OracleClientFactory, Oracle.ManagedDataAccess, Version=4.122.19.1, Culture=neutral, PublicKeyToken=89b483f429c47342" />
</DbProviderFactories>
Are these entries in your machine.config file?
Also, from my reply below:
"One other thing, If you don't wish to get a warning message about the inability to Save the connection info for older Frameworks like 2.0, 3.0 and 3.5 then select the settings arrow at the top of the editor and under Save uncheck that option for All framework availability combinations"
