>Hell all
>
>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)?
No, with buffering, most of the time there is really no nead to worry about explicit locking.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
