>SNIP
>>Could you present a scenario that explains the differences I described between how DO FORM and MODIFY FORM behave, based on cache.
>
>Sadly, no, and that's why comments from a VFP Team member would be so helpful here!

It is dissapointing that they don't, at least, acknowledge it. This DO FORM / MODIFY FORM issue only affects the developer, but how about how VCX included in EXE work together - which generates run-time errors affecting all users. Both issues seem to have to do with memory, maybe caching, and interaction between VFP and the OS.


>
>I could make a GUESS... MODI FORM, for reasons unknown, wants to ensure that it uses fresh copies of tables for it's DE work so it FIRST CLOSES with PURGE (of buffers) any open tables. Since it can only do this to tables IN THE SAME (application) PROCESS, having the tables open in some OTHER process makes THOSE CACHED tables available to the MODI FORM process too (cached data is available system-wide).
>
>Now this makes little sense because it shows clearly that MODI FORM is really just wasting its time in doing the operation.

That's what I asked for - a guess that makes... a little sense ;)

>
>>
>>
>>>>
>>>>>
>>>>>cheers