The only thing that has to change is the connection string.  The database is not hard coded into the business objects.  So if you create another database, all that you need to take into account is your connection string...or more than likely, just the database portion of the connection string.

Here is an idea of what you could do after your standard connections have already been established:

       

In our application, we need to give the user the capabilty of creating additional databases so that they can manage several companies.  What would be the suggested steps for doing that?

At the moment this would require you to write some code to redirect the database to a different name...however, this is something that has been requested more than once (the ability to have a dynamic database name).

New to StrataFrame.

We are generating objects using the DB deployment toolkit, Business object component class and the Business Object Mapper.

It appears what is generated for the DB name is our development database name.  When deployed is this overridden by what the user specifies as his/her database name?  Or do we need to write code to override?

Ben