>Hell all
>
Hell right back at you :)

The only reason I can think of locking a file like that is if generating a new primary key, to ensure only one instance of your app gets the next key.


>Ok...new job, new application to learn...very old Fox code ported up through VFP8.
>
>All through the application we're doing explicit header locks - doing what ever to the table, then unlocking and flushing memory. Granted these are huge files (800 meg + ), but prior to this job I've never worried about file/header/record locks and let VFP handle that for me. Of course, I also went to file buffering/transaction handling along the way.
>
>Is there any reason WHY (other than old code)?