Steve,

I certainly agree that the data would be buffered, but bufferred does NOT (necessarily) mean unavailable! One gets the distinct impression, with nested transactions, that VFP makes certain buffers available depending on sequence of TableUpdate/Commit/access.

But distinct impressions have failed before.

good luck,
Jim N

>Hi Jim,
>
>I'll check it out. I agree with what you said, but I'm not sure that's how it works. See my reply to Barbara to view what the code looks like. Note that it's not in a nested transaction. It would also seem that what I'm seeing is how Andy Neil's article (Where the data goes to hide - Feb '98 Advisor) has it too when he states that "In a case where users report seeing differnt values in the same data source........". He doesn't really get into nested transactions but it seems to me that regardless of the level, all items within a transaction are buffered until the last END TRAN is reached. But again, I'll have to check it out with some experimenting I guess.
>
>Thanks,
>Steve
>
>>Steve,
>>
>>I *haven't done it myself, but I do think that that is one very important purpose of nested transactions - to let data get UPDATED in tables so that it is available to SUBSEQUENTLY-issued accesses against that data.
>>You should be able to do pretty much whatever you need.
>>
>>good luck,
>>Jim N