this is indeed a different way about it, but doesn't get around the root of the problem: when VFP tries to lock a record, it usees the SET REPROCESS setting, and if it is anything but 1, will keep attempting to lock the record, depending on the setting. During these successive attempts, VFp gives the user a message "Attempting to lock..." and this qualifies as UI, a no no for an In-Proc server.


>David (and David) and Erik,
>Couldn't you just handle the LOCKing issues programmatically. Bracket the INSERT with a RLOCK(0), or perhaps even an FLOCK(), depending on the locking being done in the application?
>Charlie
>
>
>>David (and David)-
>>
>>I think the problem is arising from VFP's habit of putting up the "Attempting to lock..." message that happens when REPROCESS is anything but 1. As for the solution, I don't know- I am very curious to see this myself.
>>
>>do you have
>>SET TALK OFF
>>SET NOTIFY OFF
>>?
>>