Thanks.

>As to the second part, Fox has always worked that way - it seems to treat all the fields in one record as one big field, and doesn't write until you move off the record. Even without buffering, there is implicit record locking under the hood, and there is no mechanism for field locking.
>
>The first part may be something in the nature of the check box, or the nature of the data handling (assuming your code isn't causing it in some unknown way). I tried it with 2 copies of VFP, USE MyTable / BROWSE, hopping back and forth. I was unable to produce any unexpected behaviors when modifying a logical field, so it must be something the checkbox does.