Bob,

>Most of the code is in the UI. The main reason we are wanting to keep the UI completely in FoxPro is a requirement for a more or less seamless UI and a seamless integration between the .NET and FoxPro code.

The reason I ask, is I've helped with many VFP-to-.NET conversion projects and I've found that if the majority of the application logic is in the UI, it's easier to recreate the UI in .NET and create new .NET business objects. It's extremely difficult to muck through the existing code, pull it out into .NET objects and call them from a VFP front end. That's because there is so much untangling you have to do when UI code mixed in with business logic.

Regards,