>>>>>What about subclassing the preferencesform in aforms for the app to do & appear the what you want... then use your own abstract factory lookup table to substitute the default preferences form with your own?
>>>>
>>>>That's not a bad idea, but the user will be choosing the database they want to load through an option on the preferences form.
>>>
>>>Why not have that set as a child of the users table. When they log in you get which dbc to load?
>>>
>>>___Stephen
>>
>>Stephen,
>>
>>I'm not sure what you are saying. Could you elaborate?
>
>I would either add more columns to the users table or make a child off it that contained in house user preferences, For my past works it contained printers that they could choose. Instead of Prompt I put up a grid to show them INVOICE Printer.
>
>In your case it could contain the dbc that you want them to use. This way they never have to think about it, and that makes our life easier!
>
>I have not done this in MM yet but it's a matter of time.
>
>__Stephen

Stephen,

The problem I'm having is that the deLoader picks up which database to use from the metadbc. In order to use the multi-database functionality in this situation I would have to recreate each dataenvironment with a different database key. What I would like to do is use the same database key for both databases--afterall, the databases are exactly alike but in different locations. What I can probably do is modify the preference form to save the path information to with the same database key. I'm still studying the code to see how all this works. It's very elegant, but in this situation I'm going to need a different unique idetifier than the cKey field in the metadbc. I'm also going to need a way to change the ldefault field so that the program has a way to know which is the primary database when the user selects the option from the preference form. I'm getting close to solving the problem, but it is alot of work. The framework supports multiple databases, but not two copies of the same database. For instance, I would love an option on the preference form to switch between a production and development database with simply one mouse click instead of having to actually change the path information to the database. Just set the paths once and switch back and forth at will! I'll let you know how things turn out once I'm finished.