>>>I have my main application... view, edit, report on data.. etc.
>>>
>>>Then there is a 'automated' piece to the system which is to run on a dedicated server, which will download files from external sources and process them into the main applications data tables on a regular schedule. If I want to share any of the business objects between the main application and this automated piece, what would be the best way to handle it.
>>>
>>>At the moment though... in the automated piece, i'm not using any business objects but just accessing everything through SPT. ( all the apps data is in SQL server, can't wait to see any enhancements in your next version for SPT *s*)
>
>>Sounds to me like you have a set of bizobjs processing data from the server, and another set of objects taking that data and loading it into the app. Why not compile the sql bizobj's into a COM server and let your application bizobj'S call it when needed.
>>
>>If this is the case, the documentation has a good example of how to create a COM server, and what files will be necessary to be included in the project.
>
>James,
>
>If i understand you correctly, I'd then be putting all my shared business rules into a COM server. Which having all of them in one spot is nice. But for the minor work of compiling two projects, instead of one, I would rather have all these rules included in each piece.
>
>Anthony

Actually, you'd only be putting the bizobj's you need in the com server. I do this sort of thing all the time. In fact, I often compile some of my bizobj's into dll's if I know that they are going to have a very specific purpose or need to be used with ASP.