yes, and that's exactly what i'm saying should be one table, not one per customer. its typically a poor design decision to say that you need to create a new table for each customer that gets added. let's say you start w/ 3 customers. next week you pick up 3 more, and each week you double.
in a few weeks you need to create 20 then 40 then 80 tables...
it's a management nightmare.
also, since you're hosting the system, you're going to want to collect statistics and tell customers how they rank against one another at some level. it's much more difficult to automate this over numerous tables than it would be if it's all in one table.
what is your concern, or really design choice, that makes multiple tables the most viable option?