ROFL - the product manager for VFP can only recommend a book that shows a VFP programmer how to transition to the latest MS vision rather than saying "don't bother with this stuff, VFP will work for you forever!". I think they call this "the handwriting on the wall." How about a good book on Delphi/Kylix, there seems to be a bit of interest in those langauges - and they're multi-platform too. If you have to make a change don't just accept the "vision" of one person, open your eyes and have a vision of your own. Think about it, who gains in a change from VFP to .NET, not the developers because VFP was perfectly capable of doing what was needed. So, this change must be for someone else's benefit, at our cost. Bottom line, if you have to pay for something then look around and make sure you're getting your monies worth, which means look at other vendor's offerings such as Delphi, Power Builder, etc. etc. Just my humble opinion - "JMHO".
Scott