A not to clean approach which would be to put all the common elements in one library and all the specific ones in separate libraries for each or your versions of the application.

You could then have these libraries included in a single project or include them at will in several project - whichever feels more comfortable.

Alex


>Hi All,
>
>I am writing an application for use by different users in the same vertical marketplace. Each of these users will have their own version of the application(.exe) and their own tables etc. My question relates to the MM project structure. I do not want a different project (at least I don't think I do) for each user because there will be common classes, tables, views, etc. Each user could have unique tables in addition to the common ones, so this means different dbc's.
>
>I am thinking of having one project with seperate data folders for each user and unique .vcx's for each user that would contain only their unique classes. Common classes would be in shared .vcx's
>
>Has anyone set up this type of scenerio, and if so what are the problems, or am I overlooking something?
>
>TIA
>
>Regards,
>
>Bill