What you are describing is a "permissions" issue. What companies can a given user access.

Having a 1:M:1 between User and Company is the typical way to do do this. This allows new companies to be set up without creating separate tables, and allows for Enterprise reporting by company, etc.

Hank

>Experts,
>
>This question maybe in the realm of best practices in regards to developing software / applications for small business owners. I have a client who has multiple small businesses and requested an application that would be able to handle multiple businesses and the customers and products associated with them.
>
>What is everyone's opinon on being faced with this sort of request? My initial thoughts are to allow the user to register (for the first time upon installing), and then figuring out a way to force the user to create xx number of business profiles. Is this good practice? Any recommendations on doing this or NOT doing this?