>Hi Peter,
>
>Just a general suggestion you might be wise to consider: instead of going straight to VFP7, maybe you should first try making the transition to VFP6 SP5. I think you are likely to run into fewer difficulties, and those you do encounter, you'd probably have to deal with anyway. By the time you're ready to make the move to VFP7 (SP1), you may find that VFP8 is already out, and perhaps you can go straight to there from VFP 6. For your purposes, you could think of VFP8 as VFP7 SP2. (No doubt I'll take some flak for that prediction, but with no clear, open summary of known VFP 7 problems and no plans for another SP, I'll leave it to others to judge this for themselves.)
>
>That isn't to say you shouldn't be making use of VFP7 in the meantime, for the convenience of its developer-oriented enhancements, like Intellisense, Object Browser, etc. But since you seem not eager to introduce any dependencies on new VFP 7 features, it's quite possible that the transition first to VFP 6 would make your life easier.
>
>Mike
>

Hi Mike !

I don't think that is a real option anymore, and the first think it 'd come to is the "finding excuses" from Ed. And, some small year ago I already thought like this, "skip VFP6 and go to VFP7 at once". But another year passed ...
Furthermore, I had the attempt when VFP6 came around, and that one failed too heavy. Okay, it was no SP's but anyway.

Lastly, I sure want to apply VFP7's features (let's say even more VFP6's), it's only that I won't apply them during the traject of the transition.

Thanks for the good advises, as always.
Peter