Well is the speed still bad after you DO FORM and then return to modify the form?

One possible explanation is that MODI FORM is opening the tables and DO FORM has the opened (now cached by the OS) tables avaqilable.

But that should, one would think, make the next MODI FORM fast. [unless MODI FORM feels it has to re-open tables freshly in case of changes by outsider proesses]

dunno, really (as you can tell < s >)


>Actually, for us, it started to happen with VFP 7, but it's probably just a coincidence, I don't think is version related. I know that it is related to the number and the size of files in DE.
>The strange thing is that DO FORM is fast but MODIFY FORM is slow, why would they be different, it is the same data that is accessed.
>
>True, if the files are opened in code, for ex. in form's load, MODIFY FORM is fast, but having the files in DE has its benefits (drag and drop, visual design, automatic closing...) so I'd prefer to have them in DE.
>
>So, right now you don't see this diference, or it is you just don't use DE. Could you do a test - like add a big file to DE and compare MODIFY against DO?
>
>Thanks.
>
>>I can recall this happening several years ago with a huge project in VFP 5.0. As I recall, by removing the DBC from the project we resolved the problem.
>
>>When I have the option I prefer to not use the data environment of the form and never use it for reports. My preference has been to open the tables first and then the forms/application. After a few years you forget why you do anything and just become a creature of habit! :)
>
>>
>>
>>Tom