If it is a windows app, then create a mmWindows app with a class in there that has methods that call your business object methods. They can instantiate the windows app dll instead of the business object dll. You don't need any forms to show to do this and it is the best way. This way you can handle all the mm stuff on your side. You can do this by just creating a class library that has all the mm stuff also but you have to figure out all the mm stuff you need to include that way.
Tim

>Yes, it is being used in a non MM app.
>
>>Hi Dan,
>>
>>Is this business object assembly being used in a non MM application? The business objects need to access the data via the connection defined in the application configuration file and yes the factory is used. I am not sure what all would be needed to be able to do this without an mmApplication in the mix. I would be more inclined to create an mmApplication that uses a business object project and sent them that dll. This is what I do for WCF services is create a little mm application dll that access the mmWCF data. Then I can distribute that and it has the calls to the business objects along with all the needed mm app stuff included.
>>
>>Tim
>>