Hi Erik,

>Using local views, if you set a breakpoint after the requery(), bring up >the underlying table in the debugger and scroll to the field it's refreshed >and will work just fine when you continue.
Most of the times different behaviour when run stepping through in the debugger can be attributed to missing doevents in code - the event que will be taken care of whenever you step to the next line.
Since you mention the browse, I think the key here is NOT the debugger, but the browse. Try suspending without calling the debugger, browsing from the command window: this should work, because the browse does an implicit RLock(), which is working in the _safe function of my code.

>I've been searching for the missing setting that will magically make this >technique work, but I think we've dug up a bug here.
You could try flushing the table and sprinkling in doEvents, but I believe the correct way is using explicit locks. You see that I cut the inkey interval - it is fast enough. It still feels like a bug though...

Regards

thomas