Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Slow save in VFP9 comparing with VFP8
Message
From
30/05/2005 18:55:05
 
 
To
30/05/2005 18:01:51
General information
Forum:
Visual FoxPro
Category:
Other
Environment versions
Visual FoxPro:
VFP 9
OS:
Windows XP SP2
Database:
Visual FoxPro
Miscellaneous
Thread ID:
01015381
Message ID:
01018607
Views:
10
SNIP>
>No one to blame here I guess, I know what VFP is not strong typed and that I have to deal with that, and I know also that the clause FORCE is not mentioned with FLUSH in VFP8 Help.
>
>But I could be wrong; maybe what I described here is not a possible scenario for a perfect programmer that can write perfect code.
>
>In any case, I don’t think your hurtful words towards Nadya add any good to the process of learning that you can’t go happily using FLUSH FORCE for all work areas opened without expecting poor performance, as Jim Weil explained it very well. I’d rather be thankful to Jim Weil and Nadya for letting me know their experience.

There's just a bit of history here, Juan, that prompted my comments.
Looking at the specific example, it was mentioned that there was a conversion from VFP8 to VFP9 UNDERWAY.
Since VFP8 does NOT mention "FORCE", it's a pretty safe bet that the "offending" line was added for the VFP9 conversion and so was also very recent. That VFP8 later didn't choke on it was not helpful, that's for sure.
Now when I change some code and get unexpected behaviour the FIRST thing that I do is to look at my RECENT changes. But here it was the Mere Mortals framework or VFP9 that was blamed!!!! Even though "FORCE" was recently added to the SAVE routine! What was the described problem again... a slowdown on SAVE, wasn't it???????

The history... how about naming 2 or 3 downloadable RI Builders and declaring them "unsuitable" or "buggy" then carrying on a long discourse coding their "own" that showed there was little knowledge of the actual requirements/restrictions in the first place?... How about commenting on some threads that (paraphrasing) 'I'll use the download too as soon as the writer (naming the name here) fixes some bugs that I have discovered?... How about (paraphrasing) 'My colleagues don't seem to appreciate when I make suggestions to change their code'.

I find far more noise than "learning" coming from threads by the originator in question, but nevertheless I later wished that I had just shut up on the matter. But I unfortunately let it get to me. I've told myself to be extra tolerant next time. I hope I can do it.
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform