Hi!

Now I solved the problem! It realy depends on the SQL Server ODBC Driver Version! There must be a bug on the Version 2000.81.xxxx. After instaling the Security Patch for Mdac, the Version is 2000.85.xxxx an the problem is solved! The Patch:
ENU_Q832483_MDAC_x86.EXE

:)

Greetings from Germany and thank you for your Help


Hi!

Thanks to you for this information.

Of course, now i have lost the trust in the SQL Server ODBC Drivers,
and must add code for checking the SQL Server ODBC Driver version;
if a not certified version is found,
then set the client application to read-only mode

This issue reinforces my conviction:
to use the ODBC parameters less possible

Fabio