Hi Jeff,

The code you posted shows optimistic locking, not pessimistic. Can you clarify that?

>I'm working on an application that is having some serious, though intermitant, conflicts in the multiuser enviornment. I found out there's a VB programmer that is writing data to the memo field. He said he's using pesamistic locking, but I wonder if ADO might be locking the table header in the memo file. I'm starting to write some test code right now to see if I get contention. Apparently the VB code is not called very often, and I don't have conflicts very often.
>
>below is connection code and record set code I received from the VB guy.
>Any thoughts apprecitated.

>connstr = "Provider=MSDASQL.1;Persist Security Info=False;" + _
>             "Driver={Microsoft FoxPro VFP Driver (*.dbf)};" + _
>             "UID=;SourceDB=" + Source + "\;" + _
>             "SourceType=DBF;Exclusive=No;BackgroundFetch=No;" + _
>             "Collate=Machine;Null=Yes;Deleted=Yes;"

>TJrst.Open sqlstr, TJcnn, adOpenKeyset, adLockOptimistic
>
>
>TJrst.Update