I want to make a type of online application system where users can install modules into there account like facebook.com. I am a little confused on how to do this because i have no idea how i would set up the database.

The main code will be PHP but the data will be stored in a MySQL database. I dont want to create a completely new table for each module i have. But each module willbe different and consist of different functions/data.

These are some example modules that would be installed into a users account: Notepad, Blog, RSS Reader, Favorites system. See, i would just make one table called "Site_modules" but what about when the data has to be stored in multiple rows or somthing?

Thanks for help in advance!

List the modules in a modules table and make seperate tables for the modules contents. I know that's not what you want to do but it's the most efficient, productive, and flexible way to go.

That actually what i was thinking of just before i got on the computer...

But i have another question, what if i have like 200 modules? I mean wont that become a huge database, and will my database become slower?

naturally the more you have the slower it gets.

if you look at this forum for instance. if you had it with 10 posts and 2 users it would probably be faster. because it doesnt have to query the 35000 odd users and the squillens of posts.

I have seen the dbs of a standard vb install. .theres ALOT

basically keep the tables and database optimised clean out the stuff which is dead and ou shouldnt have any problems

It's like with a harddrive and a library system. Keep it organised, it's actually easier to search through. Even index it if you can. That will help it to find information quicker too.