>>>Take VFP of of VS BOX, VFP will go into Another Box(COFFIN).
>>>
>>>I seen the signs 2 years ago and I am well Into VB 6 & Starting on VB 7. I still maintain a lot of VFP 6 apps for my clients but no new development. Thats what M$ wants VFP developers to do And I have gone that way, not the best way but the only way I can out food on my table.
>>
>>I don't think it's a foregone conclusion that VFP dies if it's separated from VS. Regardless of the box you put it in, the only thing that really matters is that Microsoft seriously supports it. If they do, the rest will take care of itself, and I'm sure the VFP product team can figure out what to do with their new-found budget. If MS keeps hiding VFP, regardless of what box they put it in, it will turn into a rotting corpse. Any fool can see that Microsoft's behavior towards FoxPro has been inconsistent and can't possibly be justified by any rational argument. I wish Bill Gates would be satisfied with the fact that he was smart enough to buy the product, if not to invent it. The adopted child syndrome is just too painfully obvious.
>>
>>As to MS's grand strategy to force us into swallowing VB, I predict it will backfire. I spit on VB. If MS insists on choking the life out of VFP, it's Java for me, and I'll bet I'm with the majority on this.
>
>What about us C-bodies? In spite of what markus says, sometimes there's enough time to write in C++!

I have respect for C++, but it would be my second choice after VFP and Java.
Feel free to use Assembler language if you are so inclined. I've had a taste of microcode too. That was fun, but I don't think I'll be using it on my database apps in the foreseeable future.