Uuuuugggggg!!!

Right after writing that message I found the problem. It was the old tableupdating a buffered view to a buffered table. Thanks to Nadya Nosonovsky because she mentioned that in my earlier message (to which I replied, no, of course the underlying table isn't buffered).

Actually what appears to happen is that there is an other form that does open the underlying table as a buffered table. The editing form that was causing the problem has that table in its data environment but with buffering off. I suppose that the table remains open from the first form with buffering on and it doesn't get turned off when the editing form opens.

So new question: Why? If the Data environment has a Close Tables method, doesn't that "Close" the tables. And if a table is already open when a form's data environment is called why doesn't it get the properties defined in the data environment (like buffering?)

Ken