>>>>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