Hi, IMHO, we are all just tuning ourselves into a different programming environment. The OOP Environment. And most of the tools/languages that we use like VFP or VB are gearing up for better OOPs facility. So we are not going to starve and die. Tools may come and go. The concept will remain. What ever developing tool it may be, we'll be setting attributes and writing few lines in its method. When I was a dBase III programmer, I remember the effort done to make a menu beautiful! Now, its done by somebody else and I just use it. Switching to a different environment may not be as hard as 10 yrs back. So, MS killing VFP? Fine, let them kill it. We'll find a better one! Cheers, Biju > > > I was discussing new projects with a client today when he asked "What's > happening with Foxpro?" I know what was going through his mind, Visual > Basic is in everywhere and Visual Foxpro just doesn't have a healthy > profile. > > Why is that? VFP seems to be a fine, useful language. Why does Microsoft > not push it? Is there something wrong with it? Am I charging down a > dead-end street? > > I am not satisfied with the usual answers of "Oh VFP 6.0 or VFP 7.0 or > whatever is on the drawing board", let's face it folks, Microsoft does not > want VFP to be mainstream, they are killing it softly.