At a client I am working with we have implemented a 3 character unique identifier for each client that is stored in a "company" table. We use this identifier to drive business rules etc. You can use this ID to determine what class name for a form to instantiate etc. You could use the abstract factory (CLASSES.DBF) to drive customizations as well.

HTH

Dan

>Kevin or ???
>
>I have an applicaiton the is being used by multiple clients. Each client has a degree of customization. In the development mode I have had a single project and swapped data directories (containing the dbc and all tables, views, etc) depending on the client I was working on. It worked while I only had a couple of clients, but now, with more clients its too easy to have the wrong data.
>
>I have been looking for ways to improve the situation.
>
>Refer to the base project as the parent and all other clients as children.
>
>My thought now is to:
>1. Create a project for each child using QStart.
>2. Use GENDBC to create a view script of the parent dbc.
>3. Update the child dbc with the above view script.
>4. Subclass all parent classes into the corresponding libraries in the child project.
>5. Use VCXEDIT on the dataenvironment library of the child to change the dataenvironment of the child.
>
>It sounds like a lot of work but its the only way I can think of to take care of the problem.
>
>Does any see any problems with the above plan, or has anyone a better solution?
>
>TIA
>
>Regards,
>
>Bill