Nelson,
As I noted within parentheses you need sysadmin or serveradmin role to be able to check/modify it.
Cetin

>Thank you Cetin:
>The code that you sent me, show that in both cases 'IMPLICIT_TRANSACTIONS' are off. But the code did not change the setting here is the output:
>
>Implicit transactions are off
>Implicit transactions are now off
>Implicit transactions are restored to off
>
>Several articles in microsoft talk about this problem in MDAC version 2.5 & 2.6. But this was fixed in Sp1 & 3 respectively. We updated the client with the latest MDAC but no change....
>
>
>thanks
>Neslon
>
>
>>>Hi everyone:
>>>
>>>I have one here that's killing me. We have an VFP/SQL server application that uses remotes views against a SQL server 2000. The problem is that in our location works perfectly (duh...common phrase for us programmers), but at one (only one) of our clients always hangs while querying or updating. After many days trying to figure it out we ran the sql profiler against both databases and we found that in our client's server.... every query or update is preceded by a "SET IMPLICIT_TRANSACTIONS ON". In our location we don't have that.
>>>
>>>We are thinking that's something related to ther odbc drivers. Please help ....!!!!!
>>
>>Probably, SQL server itself is configured globally that way (Server\Properties\Connections tab).
>>You can programatically check, modify it (sysadmin/serveradmin) using sp_configure globally. ie:
>>

>>local lnHandle
>>lnHandle=SQLStringConnect(;
>>'DRIVER=SQL Server;SERVER=servername;User ID=uid;Password=pwd')
>>
>>* Check
>>SQLEXEC(lnHandle, "sp_configure @configname='user options'",'curConfig')
>>? 'Implicit transactions are '+;
>>   Iif( Bittest(CurConfig.Config_value,1), 'on', 'off')
>>
>>* Turn off
>>SQLEXEC(lnHandle, "sp_configure @configname='user options', "+;
>>   "@configvalue="+;
>>   Transform(BitClear(CurConfig.Config_value,1)))
>>
>>SQLEXEC(lnHandle, "sp_configure @configname='user options'",'newConfig')
>>? 'Implicit transactions are now '+;
>>   Iif( Bittest(newConfig.Config_value,1), 'on', 'off')
>>
>>* Restore
>>SQLEXEC(lnHandle, "sp_configure @configname='user options', "+;
>>   "@configvalue="+;
>>   Transform(CurConfig.Config_value))
>>SQLEXEC(lnHandle, "sp_configure @configname='user options'",'sqlConfig')
>>
>>? 'Implicit transactions are restored to '+;
>>   Iif( Bittest(sqlConfig.Config_value,1), 'on', 'off')
>>
>>SQLDisconnect(lnHandle)
>>

>>OLEDB and ODBC drivers automatically turn if OFF on connection. So I think you're right suspecting the driver.
>>Cetin