>Dave,
>
>Sadly, what you say is true - I've seen the exact same attitude here too!
>
>Rumours and innuendo can be very effective, as has been proven by our shared experience! Too bad "nice" rumours never seem to work that way.
>
>Cheers,
>Jim N
>
>>It is easy for me to relate to Rebecca about the demise of FoxPro. Because when upper management hears all these rumors it makes them want to wait to see what will happen with Fox in the furture. They are so afraid of moving to something that may not be supported in the future that they are willing to continue to develop in FPW 2.6. I know this sounds crazy but I'm watching it happen right before my vary eyes. They tell me that they don't want to re-tool again.
>>
>>My reply to this was simple good luck finding a tool that won't need to replaced or updated in then next five years. This reply fell upon deaf ears.
>>
>>>Rebecca,
>>>
>>>Why not just wait until it actually happens???
>>>
>>>I'm betting that such a demise is YEARS away. Furthermore, once "shot" it will live a very long time before it is actually buried, and there will be PLENTY of time to move into something else. COBOL has had the same rumours since the mid-70's, and its still here!
>>>
>>>Cheers,
>>>Jim N
>>>
>>>>It appears as if Microsoft is slowing withdrawing from supporting Foxpro again. There are no materials available for the Foxpro certification and there is no information about the next version of Foxpro which normally would be in beta by now. Any one have any ideas or knowledge about this???
>>>>
>>>>Thanks.


Just to add my 2 cents worth. A couple of years ago, I was seriously questioning the time I new that I'd have to invest to learn 3.0 when it came out. If you think the rumors are bad now, then they were worse. Although we all may not be overly happy at M$ for their apparent lack of effort with VFP, I think that we as VFP developers are on far more firmer ground today. I believe that it was Roxanne, on her commentary about DevCon that stated that there are companies out there having problems with PowerBuilder and Delphi apps and are looking again at FoxPro as a viable solution. To brighten you all up a little, not all companies shun FoxPro. I can look in the Sunday employment section to find enough VFP positions to know that I don't have to worry should I lose my current full-time job (writing a huge medical analysis app in guess what....VFP 5.0). My independent work has just signed on as a sub to an insurance company rebuilding an app in guess what....VFP 5.0. Clearly everyone on this board is working with FoxPro so I think that we are all going to be around for some time to come. Although M$ has made our marketing efforts more difficult, I find that I can usually overcome these and get a client to see that the minimal expense of VFP, when compared to other per user licensing arrangements, and the proven technology of Rushmore far outweigh the comments that they might make. We may not quite yet be standing on cement, but at least it's not the quicksand of a few years ago.

Steve Despres