>So you are suggesting that we have a separate VFP application running at the same time as the VB application and just switch to that application when necessary?

If you need to reuse the VFP forms without rewriting them in VB, that's basically your only option, AFAIK.

Can I ask why you need to keep some VFP forms if you are porting the app to VB? Why not rewrite the whole thing in VB? Why not put the business portion in a VFP COM?

>Do you know of any way that VB could host an ActiveDoc object? Perhaps with a browser window embedded in a VB form? This is getting so complicated...

Sorry, but I'm not familiar with ActiveDoc.