Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 5 of 5 total
Thread DBISAM ODBC driver for Visual Studio (Version 4.40 Build 1) & .Net Framework 4.5
Thu, Feb 19 2015 7:15 AMPermanent Link

Ajay Phaltankar

Hi,

I am evaluating a trial version of DBISAM ODBC driver for Visual Studio (Version 4.40 Build 1).
I am connecting to a DBISAM table from .Net application using system DSN.

I found that,
1. This driver works perfectly fine for .Net frameworks up to version 4.
2. But it fails with .Net Framework 4.5. Where it raises exception while opening a OdbcConnection.
Exception: "ERROR [IM014] [Microsoft][ODBC Driver Manager] The specified DSN contains an architecture mismatch between the Driver and Application".

Is there any workaround?
Or Is there any plans to release a newer version of driver supporting latest .Net framework 4.5+?

Thanks,
Ajay Phaltankar
Thu, Feb 19 2015 8:15 AMPermanent Link

Raul

Globestar Systems

Team Elevate Team Elevate

On 2/19/2015 7:15 AM, Ajay Phaltankar wrote:
> 2. But it fails with .Net Framework 4.5. Where it raises exception while opening a OdbcConnection.
> Exception: "ERROR [IM014] [Microsoft][ODBC Driver Manager] The specified DSN contains an architecture mismatch between the Driver and Application".
>
> Is there any workaround?
> Or Is there any plans to release a newer version of driver supporting latest .Net framework 4.5+?


While i don't use this myself the error message seems to indicate a
mismatch of 32 vs 64bit issue (either app is 32 and DSN if for 64bit
driver or other way around).

Are you sure you're using the right one ?

See this FAQ also :

http://www.elevatesoft.com/supportfaq?action=view&category=dbisam&question=odbc_driver_64_bit

Raul
Tue, Feb 24 2015 6:32 AMPermanent Link

Ajay Phaltankar

Thanks for your response Raul.

This is not 32 vs 64bit issue. As I said earlier that, this driver works perfectly fine for .Net frameworks up to version 4 on the same environment.

Thanks,
Ajay


Raul wrote:
>While i don't use this myself the error message seems to indicate a
>mismatch of 32 vs 64bit issue (either app is 32 and DSN if for 64bit
>driver or other way around).
>
>Are you sure you're using the right one ?
>
>See this FAQ also :
>
>http://www.elevatesoft.com/supportfaq?action=view&category=dbisam&question=odbc_driver_64_bit
>
>Raul
Sun, Jan 6 2019 9:26 PMPermanent Link

John Easley

Bumping this thread because I'm having the same exact problem...

John


Ajay Phaltankar wrote:

Thanks for your response Raul.

This is not 32 vs 64bit issue. As I said earlier that, this driver works perfectly fine for .Net frameworks up to version 4 on the same environment.

Thanks,
Ajay


Raul wrote:
>While i don't use this myself the error message seems to indicate a
>mismatch of 32 vs 64bit issue (either app is 32 and DSN if for 64bit
>driver or other way around).
>
>Are you sure you're using the right one ?
>
>See this FAQ also :
>
>http://www.elevatesoft.com/supportfaq?action=view&category=dbisam&question=odbc_driver_64_bit
>
>Raul
Fri, Jan 11 2019 11:36 AMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Ajay,

<< 2. But it fails with .Net Framework 4.5. Where it raises exception while opening a OdbcConnection.
Exception: "ERROR [IM014] [Microsoft][ODBC Driver Manager] The specified DSN contains an architecture mismatch between the Driver and Application". >>

As Raul indicates, this is an issue with the bit-ness of the driver vs. the host application.  You need to make sure that you're using a 32-bit driver with 32-bit applications, and the same goes for 64-bit applications.

More information:

https://stackoverflow.com/questions/8895823/the-specified-dsn-contains-an-architecture-mismatch-between-the-driver-and-appli

Tim Young
Elevate Software
www.elevatesoft.com
Image