> Sometimes, I have an INSERT INTO which generates "file is in used by > another user" which result in a fail. > > I have SET REPROCESS TO 2 SECONDS. > > Does this mean that during that 2 seconds, the INSERT INTO was unable to > lock the header? That seems likely. I wouldn't change the SET REPROCESS time right away, rather I would have a look at why the header was locked for that long. Do you have other routines that issue an FLOCK() and then do a bunch of processing? Do you use pessimistic buffering? Is someone hitting your tables with something other than VFP? I've written a routine as part of my framework that indicates to a SysAdmin person exactly who has what screens open. This could also be expanded to include the function/field/etc. in the screen. You might want to consider something like this as well, just for troubleshooting. /Paul