Hi Arto,

When we approach milestones, we ramp up with vendors, contractors, etc. You know the "just-in-time" philosophy for inventory? We sort of follow a similar track for VFP ... it allows us to be agile when needed and not cumbersome when not. Don't let the raw numbers mislead you.

>I hope that Sedna add-on is not going to be "the last person or shop steward" or even among of them who switches off the lights and closes doors for factory shut-down? But with the transparency policy we will soon see?
>
>
>>Keep in mind that the VFP team now (and with VFP 9.0) is under 10 people while people working on VS 2005 and the .NET Framework is well over 1000.
>
><g> Hmm...
>
>

>FUNCTION VFPHope()
>
>STORE VFP_team_count TO nVFPTeamCo
>STORE Global_VFPers TO nVFPUsers
>STORE VS_NET_team_count TO nVS_NETTeamCo
>STORE Global_VS_NETers TO nVS_NETUsers
>
>STORE (100 * nVFPTeamCo) / nVFPUsers TO nMS_VFP_Efforts
>STORE (100 * nVS_NETTeamCo) / nVS_NETUsers TO nMS_VS_NETEfforts
>
>?ANALYZE(nMSVFP_Efforts)
>?ANALYZE(nVS_NETEfforts)
>?ANALYZE(nMSVFP_Efforts, nVS_NETEfforts)
>
>ENDFUNC
>
>FUNCTION Analyze(pnEfforts1, pnEfforts2)
>
>* Your code here
>
>ENDFUNC
>

>
>Analyze() can be even upgraded in some future with variables like:
>
>nVFP_FutureVersionWeightValue_to_Users or
>nVFP_FutureVersionWeightValue_to_Markets
>
>AT
>'FOXer' since 1984