>All
>
>Every so often clients complain that SQL Server applies 'locks' in records used by our apps, preventing access by others.
>
>The app in question uses Remote Views. I know of no way that a RV can leave locks in SQL Server- that sounds like pessimistic rather than optimistic behaviour and RV can only be optimistic against a C/S backend. So this sounds like something internal to SQL Server.
>
>Now a customer has come back confirming that a certain module causes the problem.
>
>The cuprit is a Remote View that uses the 'fetchmemo' cursorsetprop() option so that (very large) text fields are not pulled for every row, only for the small subset of rows needed.
>
>Closing the view solves the issue.
>
>Is this just us, or does using fetchmemo as per VFP documentation leave some sort of lock in SQL Server? Could it be a combination of connection sharing and fetchmemo?

A SWAG, but are they running a different OS for their production SQL Server box than your test machine? Differences in OpLocks settings?