Hi Jensen..

Of all the responses, Roxanne has provided the most insightful analysis. As far as limitations, every tool has them. The goal is to minimize them. One thing I would ask is why you need what you describe as a true object oriented tool. In the bigger world of OOP, you won't see articles on VFP in JOOP. I don't think they had VFP sessions at OOPSALA. The mainstream texts on OO don't mention VFP. So, in the OOP arena, VFP itself isn't even a bit player. Keep in mind, VFP is OO. But you asked the question of how VFP compares, ranks, or otherwise in the OOP arena. As a former co-worker of mine was fond of saying, English is a precise language...

I agree with Rox here that you may be approaching things in reverse order, the tail wagging the dog if you will. What does your app need to do? What are the data requirements? How will it have to scale, in terms of data size, reach, etc. What sorts of architectural requirements are required. Check out the thread on VFP vs. VB. I address a lot of these issues in that thread..

As for multiple inheritance, I wonder if you would not mind expanding on why you think you need it. Specfically, is it multiple inheritance you are looking for, or the ability to implement multiple interfaces..???


>I am choosing visual foxpro for our development platform on a financial application, we need a true object oriented platform that can rely on, can anyone tell me how visual foxpro does in the OOP arena? Does it pose any limitation in oop development in comparison to the other oop development tools? What we look into now is the ability to do multiple inheritance?
>
>Jensen Lee
>ACO