If you assume that the data on a single server will be only for related companies, it may not matter.

I had a client with several Companies and we ran all of their apps from a single database with a company ID in each table. There was not much concern over the security since they all belonged to the same "family". There was more concern over splitting of responsibilities. For example, all of the Accounts Payable transactions were in a single table but each of the companies had their own AP department. What we did in that case was to add a filter on Company ID based on the users's ID for all of the queries and remote views.

That approach kept open the option of running Enterprise wide reports.

Ken

>You presume incorrectly. I neither for nor against it. I was interested in how security of data was implemented in that particular case.
>
>>
>>From Sergey's message I presume that he is not much in favor of putting records of multiple companies into the same tables.
>
><snip>