>>>Hallo Cetin !
>>>Thank you for your quick answer, but i'm not quite sure wether your answer has something to do with our problem?
>>>
>>>We have no problems with our local foxpro cursors
>>>
>>>We send an sql-command to an external maxdb server to load a record into a form !
>>>
>>>When inside the IDE the "automatic transactions checkbox" in extras-options-remotedata is marked, foxpro does an automatic "commit" after each sql-command.
>>>
>>>so our search command (select ...... from .... with lock optimistic) creates a look entry in the
>>>maxdb locks table and the automatic commit deletes the lock entry immediately
>>>
>>>when we uncheck the "automatic transactions checkbox" in extras-options-remotedata and do the same select command a look entry in the maxdb locks table is created and can be used for our problems until we do an expicit "commit" later
>>>
>>>our problem is, that this wanted behavior only works, when we start the form from the IDE,
>>>the exe still seems to do an autocommit ????????
>>>
>>>Best Regards
>>>Albert
>>
>>Albert,
>>When transactions are set to manual I only saw it autocommit if the connection is closed (bug I think and might be fixed in VFP8 or later).
>>Cetin
>
>Albert,
>Tested under VFP8 SP1 and bug still exists. As soon as connection closed an explicit Commit tran gets to server. Instead of depending on it I think it'd be better to explicitly start your transactions with 'begin tran'.
>Cetin
It is not fixed in VFP9.
In VFP9 exists a new ( funny ) workaround property
SQLSETPROP(nStatementHandle, "DisconnectRollback", .T.)
