Let me explain what I think documentation is.

Documentation is something almost all businesses begin to do. And at some point someone decides that it's not so important to do it right after (or before) modifications to a module are made because the time is not available. The app has to me modified as quick as possible. And at some point for whatever reason someone forgot to do it (after time allowed to do it). So from that point the documentation is worth close to nothing because can you can't really trust it now.

>Documentation - what's that? :o) You are fortunate if you landed in a place with actual documentation! :o) I've never seen it.
>
>
>
>
>>Hi Walter,
>>
>>It's a sad situation if Microsoft couldn't have:
>>a) been able to get "data" people needed out of thousands of employees;
>>b) allowed some bright lights to step into the shoes of the masters for the VFP Team.
>>
>>The new job is going slowly - reading documentation all day so far.
>>
>>cheers
>>
>> >Jim,
>>>
>>>I guess the business decision is not so much about money, but a technical one.
>>>Since MS has identified the data-handling gap in .NET they needed some good input on how to improve the data handling side of .NET.
>>>
>>>Now, what better candidate could they have found in YAG and Calvin? The VB.NET team really needs the experiece of the VFP team to make .NET better in the data handling arena.
>>>
>>>This essentially lead to the total drainage of the VFP teams intellectional knowledge.
>>>
>>>That does not take away that I find the current events sad, but heck, VFP9 fits our needs and will continue to do so for many, many years to come. In fact I truly think that .NET is immature in this respect and hopefully they'll improve it to a point where .NET really becomes an alternative.
>>>
>>>BTW, how is your new job?
>>>
>>>Walter,
>>>
>>>>>Jim,
>>>>>
>>>>>IMHO STABILITY (by which I mean the absence of regular "exciting" change) is VFP's best feature. It has made a lot of people in this forum happier and wealthier. And now we're going to get even more of it. ;-)
>>>>>
>>>>>All I can see is that those who are able and want to make a living in VFP will continue to do so. Those who can't or won't, will have to change.
>>>>
>>>>I take no issue with what you've written here.
>>>
>>>>But I do resent all those who are claiming "sound business reasons" for the decision when Microsoft itself has been mute on the whole subject of why.
>>>>To me it is the antithesis of a good business decision. VFP was cheap to maintain/develop, helped to sell hundreds of thousands of Windows and Office licenses for Microsoft and served a market where Microsoft has little interest (but should have).
>>>>
>>>>A move like this cannot possibly have good repercussions on "shareholder value".
>>>>The best Microsoft can garner is being crapped on for "abandoning" so many people/businesses that depend on VFP and don't need anything more high-falutin.