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
?

>David,
>
>Do you have an Error() method that is logging the real error that might be causing VFP to want to kick up some sort of dialog box?
>
>You might also try temporarily building it as an EXE server so the UI error won't mask the problem.
>
>>I had an VFP automation server running which does some INSERT INTO in some heavily used tables.
>>The INSERT INTO ... command is sometimes triggering the "User-interface operation not allowed at this time." error 2031.
>>
>>I've got SET REPROCESS TO 10
>>I'm now trying SET REPROCESS TO 20 and that will probably help
>>
>>Any suggestions as to handling on non-attended INSERT handling?
>>
>>Does VFP always display a "WAIT WINDOW" style message while attempting to get a header lock with insert? Can it be turned off so I don't get that error?
>>
>>Should I modify the error handler to simply keep retrying if the line that caused the error is an "INSERT..." ?
>>
>>Help appreciated.