>>hmmmmm not sure about this and it definitely would extend the development phase. I feel more comfortable with VFP because it's the tool I've been using for years but we have to plan thinking on the future though. I've heard VFP 9 will be .NET compliant, how true is this? What's the tentative release date? Unfortunately we can't wait until next year to start on this new project.
>
>
>Oh I didn't mean to stop or change development plan. ie: I deserve my full regular worktime to app development with VFP.
>At home (or at times I want to take some off time from the project I'm working on:) I read the C# books, create and test code. Hard part is to balance with family and computing :)

Yeah I know what you mean :) This is about the same method I use to learn new things.

>Honestly I have no comment about VFP9 yet. OTOH reading the architecture of .NET (yeah did at least once:) I can't see a solid reason why VFP can't be a .NET language (version9 or xx).

Neither do I.

>Definetely do not wait new releases to develop something. I bet many continue development with the older one even after they own new, while testing new aside (I don't believe I could be alone:)

No, you're not, here we still maintain apps in VFP5 even when we have version 7.

>IMHO such kind of 'waits' is also a killer on development of new versions. Happens with us all why not MS :) Customers hear we'd release version x+1 and hold their breath till release date, thinking they shouldn't pay for an upgrade + a new version is always better. If I can't sell existing version how would I finance the development of the next :)
>

Yes you're right, sometimes they don't even want to upgrade because they're doing good with the version they're using and think a new one will do little for their bussines.