Database Table Organization?

[jdlev]

I'm trying to decide how to setup user access to account information.

 

So you have a universal table for user login information that associates that user with an account.  That user only has access to that particular accounts information.

 

Now lets say that user has a company address.  

Should I have another universal table where every account's company address is saved to the same table, but they can only access/edit their own address

 

My_Database

-Universal_Address_Table

---Address Company A record(only company A can see)

---Address Company B record (only company B can see) 

 

-OR-

 

Should each account have it's own table for the addresses associated with it, so every account would have multiple iterations of the same structured table.

 

My_Database

---Company_A_Address_Table

---Company_B_Address_Table

 

So is one method more secure than the other?  Is there a limitation on how much information MySQL can handle, because I'm hoping for a few hundred if not thousand accounts?