[Opensource] Maintaining 2 contexts, one for Expresso tables, one for business logic tables?

[Michael Rimov]

At 01:36 PM 2/19/2003 -0500, you wrote:

>Just curious about something,
>
>For the project I'm doing, I was given a set of DB tables (around 20) to
>work with.  I am developing an Expresso app to manage the data in those
>tables.  Another component in the system (that I'm not working on) will read
>the data in the table to perform processes.
>
>The other team isn't too keen on my adding the Expresso tables to their
>database and are insisting that I use a seperate database for the Expresso
>tables.  So I need to have my app maintain two seperate contexts.  Is this a
>common thing?  I am trying to make sure that there are no problems in doing
>so.

Check out the latest EDG online with regards to other database contexts... 
you can have one context for your setup tables and another for the 'other' 
system and have Expresso treat it as one large context. [Expresso does NOT 
create the tables the other context, you'll have to do that manually.]

The key is DBOtherMap table, and adding the objects to your schema using 
addDBObject(DBobjectclass, otherContextName)

HTH!
                                                 -Mike