>Ooooh, shiver! Perish the thought! <bg> >>of course. what manager wants a product that works? What manager wants to make a significant investment in code base for which he or she would have a hard time to find skilled programmers to maintain it? Do all your projects serve the needs of a customer indefinitely? That's the advantage that VB has over Fox in the long run. There's a larger pool of talent. There's certainity as to the longevity of the product. And in the realm of emerging Internet and SQL standards, VB is ahead of the game. FoxPro has the OOP advantage, but I am sure that within the next year that VB will have all aspects of OOP. After all, they did not sign on the architect of Borland's Delphi for nothing, just a mere $3 million... Regards, Jack Mendenhall Manager, Information Systems Reinsurance Management, Inc. [ ...and GMRider added: ] Jumping in totally uninvited (but fascinated by the thread...) what gives you the idea that VB is certain to survive any amount of time as compared to any other product that M$ produces? Do we have to drag out the extensive list of products that M$ marketed quite strongly only to kill off without regard to the marketplace? Not that Microsoft is by any means the only one guilty of this if indeed guilt is applicable... In my humble opinion - they could kill VFP tonight and I still could make a good living for the next several years while I shifted to next great thing - which would NOT be VB btw..., my point is, is that nothing is guaranteed in this business and adaptability is probably key to survival. Thinking that any company's development tool is a sacred cow could leave you open to obsolesce.