Originally Posted by ShawnCplus

... ... .. why does every customer have their own table?

Originally Posted by ShawnCplus

I'd be willing to bet there is a major design flaw if every customer having their own table is the solution. Relational databases are relational for a reason so tables can form relationships based on primary and foreign keys.
these tables for example (not real SQL commands, just examples)

Help with Code Tags

PHP Syntax (Toggle Plain Text)

Customer
id    INT(10) AUTOINC PK --
name  VARCHAR(50)         |
                          |
CustomerCompanyMap        |
customer_id  FK ----------'
business_id  FK ----------.
                          |
Business                  |
id  INT(10) AUTOINC PK ---'
name VARCHAR(50)

Customer id INT(10) AUTOINC PK -- name VARCHAR(50) | | CustomerCompanyMap | customer_id FK ----------' business_id FK ----------. | Business | id INT(10) AUTOINC PK ---' name VARCHAR(50)

Creates a many to many relationship between companies and customers (companies can have many customers and customers can have many companies)

Originally Posted by itisnot_me

Ok so what i get from that is i should have a central login table which includes the company_id when create a _session with it. then with all of the data on another table i should include the company id so that i can recal it later?

Originally Posted by ShawnCplus

Like I said, that's just an example. I'd have to see what your current design is to know how to fix it.