Commented by: @alexpotapchenko

I think it is not Firebird ODBC problem.
Please read this - http://www-stage2.ingres.com/kb/article/418033

Commented by: Thomas Schwarzmüller (blacky)

I did some more analysis.
It's a known bug in MS Access, but the Easysoft ODBC driver fixed it with the option "Default SQL_CHAR".

Someone told me, he took your source code and just changed the return value to SQL_C_CHAR instead of SQL_C_WCHAR. Now it works. Unfortunately he did it only for a 64-Bit Version and I don't have the tools to do the same for a 32-Bit Version. Would anyone be willing to do this ?

Commented by: @alexpotapchenko

The attached 32-bit driver with this fix.

Commented by: Thomas Schwarzmüller (blacky)

Wonderful !
It works.
Thank you very much.

Commented by: Thomas Schwarzmüller (blacky)

Hello Alexander,
I don't know if this is the right way to contact you, but didn't find another.

Do you remember the issue above ODBC124.
You fixed the ODBCDriver Version 2.0.0 in 32-Bit and it worked well all the time.
Now I have a Windows 7 64-Bit Installation and it Shows the same problem.
Would it be possible to fix this Problem in the latest ODBCVersion of 64-Bit also ?

Best Regards
Thomas

Commented by: @alexpotapchenko

The latest ODBC driver versions with this fix in attachment.

Commented by: Thomas Schwarzmüller (blacky)

Your Support is unbelievable.
Thank you so much.

Commented by: Chris Sproß (chris63684)

Hello Alexander,

I hope this is the right way to contact you about this issue. I too am facing the #⁠deleted problem when using a char(3) as primary key. I found this issue ODBC124 here and hoped that the special version you attached would work, but with this version, Access 2003 and Firebird 3.0.2.32703 (64 bit) I receive the error "[ODBC Firebird Driver][Firebird]Attempt to reclose a closed cursor (#⁠-501)" when I try to connect to the ODBC source from Access. Using your newest ODBC Driver with version 2.0.5.156 works fine (apart from the #⁠deleted problem).

Is there maybe something obvious I'm missing? If not, would it be possible for you to fix this problem in the newest Version like you did before?

Best regards

Chris

Edit: Since I have written this I have compiled the sources with Visual Studio Community and the driver works apart from the #⁠deleted problem. I would actually be more interested in what parts of the code you changed to make it work with Access so that I can then make the modifications myself when a new version of the driver is released.

Commented by: @alexpotapchenko

Hi Chris,

I have attached patch for this issue, there is small change in OdbcStatement.cpp.

Commented by: Chris Sproß (chris63684)

Thank you very very much.

It's almost working now: Access now correctly shows the records, but only if the primary key doesn't contain umlauts (äöü). I'm guessing that the database supplies a unicode string, the driver tells access that it's an ascii or ansi string and thus the umlauts don't get converted. I'll try and see if I can add that implementation myself, but it's a lot of code.
----------------

For anyone reading about this in the future and not knowing how to build this version from source yourself:
You can download "Visual Studio Community" for free, upgrade the MsVc90.win project of the driver with it and make three changes to make it compile successfully.
Change these things in the options of the project:

1) in the C/C++ overview change the Include path for your Firebird installation (mine is "C:\Program Files\Firebird\Firebird_3_0\include", was set to "C:\Program Files\Firebird\include")

2) in Linker->Input you have to add "legacy_stdio_definitions.lib" to the Additional Dependencies or otherwise the linking of the dll will fail because they changed the sprintf functions to inline.

3) there are a couple of lines that won't compile that look like this: r = appendString(r, ";"SETUP_DRIVER"=");
Just change them to this:
r = appendString(r, ";"); r = appendString(r, SETUP_DRIVER"=");

After that it should compile and you can apply Alexander's patch (which you can do manually. It's just a few lines).

Hi Guys, can i have the ODBC patched for ms access? i can't find the attach to this tread

Thanks a lot
Br

with this fix in attachment

I have the problem that MS Access show me all results deleted ... The Firebird server has UTF8 char set but i can't change this parameter

Br

@irodushka This issue still persists on 3.0.1 (22/dec/2023) build.
Would be great to get it fixed also.

Yes, the 2.0.5 build has this issue too.
Attached is a script which generates this issue when browsing the table from MS Access.
Firebird ODBC #121.zip

Hi @jabrugger
I made a fix in the last build, you can try it.
This version magically detects that it's loaded from MSAccess and applies a patch))) So you don't need a special ODBC driver build. Hope it will work ok.

@irodushka It seems to work fine! Thank you so much!
If I find a problem I'll let you know.

Hi @jabrugger I made a fix in the last build, you can try it. This version magically detects that it's loaded from MSAccess and applies a patch))) So you don't need a special ODBC driver build. Hope it will work ok.

Hi , i also had the problem. Where can i find the last release with this patch?
thanks :-)

@MicheleFire2022 it's available at https://github.com/FirebirdSQL/firebird-odbc-driver/wiki

thanks a lot ;-)

ah.... i have an old firebird so i can't use this one :-(

ah.... i have an old firebird so i can't use this one :-(

I assume it will work with an older Firebird, as long as you use a Firebird 3.0 or higher fbclient.dll.

Closed