>>
>>Enmanuel,
>>What about both. You could utilize each at the same time and build parts with what you know best. I've a simple reasoning for myself :
>>Cash must flow
>
>I like your reasoning and I'm pretty sure the company owners like it too :)
>
>>I know 60% of VFP and 1-5% of C# (rough guess).
>Ditto
>
>>Build with VFP while continuing to learn C# and having mixtures in between maybe.
>>When their knowledge percentages come close to eachother I could decide which to pick for the next phase and I've a working app (or n-tiers) by then.
>
>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 :)
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).
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:)
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 :)

>
>>The biggest drawback of any approach I take, before I can learn any version of any language/tool fully they release a newer one :)
>
>What? I thought I was the only one :). Having a new version every 1 or 2 years is really a pain in the arse. You're starting to feel comfortable with the old version when they launch a new one.
>
>Enmanuel