Rick, > > At risk of continuing this thread that needs to die <g>. > > You mean along with VFP?<< > > Unlike so many people who consider VFP "dead", I see it > differently. I see opportunity, not the end of the road. > Partially thanks to the announcement I have several new > customers because their original developers have bailed for > "greener pastures." I am happy to mow the new lawn as my > business is growing. I diversified my skill set years ago and > continue to do so today. I am a VFP developer, project > manager, software designer, database administrator, trainer, > web developer, business advisor, and hiring agent. I can do > so many things in this industry that I really don't concern > myself with syntax or tool choices. I have always used the > best tools for the project with hundreds of acronyms and tool > sets in my past. I can learn a new language in weeks if I > choose, and have over the life of my career. I am a > certified, diploma'd, and experienced computer scientist. > > I would not let those who belittle your decision to stay with > VFP deter you from doing so. They have made their choices and > I applaud them for doing so. It takes a lot of guts to go in > a new direction. You have the right to make the choice for > your business as you see fit. You take the risks and get the > rewards, or the loss. > > Don't blame Microsoft for your past decisions, or count on > them for any future decisions. They are only one company, and > one could say, not even the leading company. The road is > littered with people who make emotional business decisions to > drive changes instead of solid business decisions. I have > observed this for years and made the same mistakes myself. It > is like a bad personal relationship. You need to forgive and > move on before you can establish a healthy new relationship. > Holding a grudge against Microsoft will not help you in your > business today or tomorrow. So where do you want to go? <g>
I relate to what you're saying very much, and I do all these things too. I am working with other tools. I've got some MySQL databases running and I'm getting through the hurdles with PHP (and even enjoying it, I might add). None of this changes the fact that I've got a quarter million lines of FoxPro code that I must protect. > >> But you don't say what their strategy actually was, or are you going > >> with they didn't have one?<< > > I could only speculate on the strategy as I was not there in > Redmond or Perrysburg. No regulars on this forum were there > in the meetings planning the merger or post-merger. Jerry just shed some light on this. Despite his caveat of pointing to the time factor, the essential ingredients are pretty much as suspected. > If they were they are under an NDA any way and would not risk getting > whacked. I have heard all the rumors that Microsoft wanted a > database, that they wanted an Xbase product, that they wanted > Rushmore (which they absolutely leveraged in MS Access), that > they wanted to crush Borland (who imploded under their own > bad decisions), etc., etc., etc. All I can say is if > Microsoft was planning from the start to kill FoxPro, they > did a really bad job of it and took far longer to try than > their competitors would have, and did with other database products. I think one monkey wrench in MS's plan was that the VFP developers exceeded MS's expectations. But, as you say, we don't have insider knowledge. And, I think if we did, we're really be fuming. Bill > Rick _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
