>>I have been moving an application written in VFP5 to VFP9. There was one view, that was not rushmore optimizable, and I have fixed that. Yet, there is no speed improvement. (I didn't write the original program, and have no contact with the original programmer.)
>>
>>I have noticed, that in the previous code, there are a number of flush statements. Especially after requery of view or update of the view.
>>
>>Would these flushes, cause a slowdown? even as much as upto 30 seconds in some cases?
>>
>>Do you think that they are necessary? i.e. Could I remove them from the code and it would still work? (Maybe do a final flush when form is closed instead of above?)
>>
>>Using the coverage profiler, the places highlighted as slow spots are the requeries, updates etc. But these lines happen before any flushes.
>>
>>I am running out of ideas on how to speed up this form.
>>
>>Thanks,
>>Mike
>
>I think they may slow down the process. Here is what we found few years ago - we had put (I did mistakenly, actually) FLUSH FORCE command in the code. And the code slowed down considerably in VFP9, but was running very fast in VFP8 (though it doesn't have FORCE keyword it didn't complain). Once we added the work alias to the command, the speed went back to normal. But we later removed the whole command, since it should not have been there in the first place.

But he does NOT have the FORCE clause... unless he is like you and anticipated the new clause way back in VFP5.

FLUSH (all by itself) in VFP9 is the same processing as all prior versions of VFP.