>I'm hoping this is the case. We've got a VB system that needs to access my VFP system to do the validations. We'd like to build the screen as a class and let them access that way, but we'd like to make sure that we CAN do the thing before we TRY to do the thing...

You want to call a VFP form from VB? Or just the data? If just the data, you're stuck with ODBC.

If you want to call a form, I think you're out of luck. VFP COM servers can't have a visual interface...

The real solution here would be to build your business logic into a business object class. That class could then be compiled into a COM server that could be called from VB or any other COM client. You'll have to build the visual interface again, but the business logic will only live in one place.