Typically, we've found that BizObjs are needed solely when data is add/edited/deleted, and you want corresponding rules to fire for those events.

Mere Mortals has a cdeLogical class (in cUtility.vcx) which is a much lighter weight class meant to be used for loading lookup views.

Use event objects to coordinate services of different objects.

That being said, I would create a BizObj for each table you plan on using for updates. That way, you know your business rules are keeping that data looking the way it should. For speed, use the cdeLogical class for pulling up any lookups. Use an event to coordinate the order of update.

This should provide you with enough flexibility, security, and speed.

If you're worried about speed (who isn't?), we have BizObjs pulling over a million records in less than a second. If things start to bog down, you might try remote views. We're doing that for a few of our more un-cooperative views... a thing of beauty our network is *not*!

Hope that helps,
---J

>I have tables of raw data, each of which need to be "data warehoused" into usable data for reports, lookups, etc.
>
>What are the best strategies to do this with in MM?
>
>I have a dozen or so aggregate/warehouse tables I need to create, which have much simple processing - i.e. just using a view to pull some aggregate data, and saving it to an aggregate/warehouse table. And each one is built off the previous one. Would I create an event object which sequentially opened each business object?
>
>That seems like overkill. I really just need to open a view, save it to table1. Open the next view based on table1 and some other table, and save it to table2. Open the next view based on table2 and some other table, and save it to table3. What's the MM way to do this? Create a business object for each view? Seems like a lot of overhead.
>
>Anyone's advice/experience would be appreciated.
>
>Thanks,
>
>David