Inheritance is simulated in Visual Basic for class modules. Essentially, your form classes would be translated into VB forms. In this scenario, your abstraction level would be Visual Modeler, not VB.


>>Actually, there is one tool that can get you part of the way there....its called Visual Modeler. If you take your VFP application, and break it down logically in Visual Modeler. You can then take that same design, and use the code generation wizard to build the VB components. The big task will like in migrating your specific business logic to VB. Then again, that might not be such a big deal.
>>
>>In the end, being able to migrate from VFP to VB has little to do with the differences in the environment. Rather, it has more to do with how the VFP app is designed. If you designed well encapsulated classes and used components, you may find the task not too difficult to accomplish.
>>
>>>Does anyone know if there is an utility to convert Visual FoxPro applications or just the forms to Visual Basic 6.0? If so, what is it?
>>>Thanks.
>
>Does support inheritance? If so, is the inheritance reflected in the VB class?