Categories vs Multiple Databases?

[daugherty.sean]

I work with several companies, as well as customer lists for each
respective company. In other words, the companies which are my
customers, each have their own set of customers which I work with on
behalf of that company. I'm trying to decide if the best approach would
be to make a database file for each company or use categories to keep
things seperate. I'm not sure what the ramifications of either approach
would be for Pocket PC syncing, reports, etc. Does anyone have any
thoughts as to which would be better?
Thanks,
SD

 

[Luther]

How about:

Companies => Accounts
Customers => Business Contacts

 

[SeanD]

I think I'm getting tied up in terminology, but I know what I typed
wasn't very clear. Maybe this will be better. Say I have 10 companies
that are customers of mine. Each company has its own set of companies &
contacts that I have to manage. The trick is I need to easily seperate
these sets of companies/customers when I sit down to work with them, so
I only work only within my customers set of companies & contacts. Now,
if I'm entering my own contacts as well as each of my customers
contacts into 1 big database, the only way I can differentiate is by
Catagories & seperate databases, right?

My customer 1 => Database1
My customer 2 => Database2
or
Category1=>My Business Name(My customers)
Category2=>Customer Business Name1(contacts belonging to customer1)
etc....

I'm hoping for some vindication that I'm thinking about this right, or
some way to re-envision the way I'm looking at the data or the program.
I would prefer to use seperate databases, but switching is cumbersome &
I suspect I'll have problems with the PDA support. Right now I'm
guessing I'll have to use categories, but would really appreciate the
input. "measure twice, cut once"
Thanks,
SD