I'm glad to hear that.
One thing troubles me tho.
what i want to know is....once ive used php to create a table with the project number as a name, [...]
I wouldn't recommend dynamically adding / removing tables. It is usually a sign of less then ideal table structures.
What would be better; create two tables, one to contain a list of projects, and a second to contain the data you currently put in your tables.
Then add a column to the second table that points to the correct project in the first table.
For example, if you have this:
- Table: Data_Project1
-
+----+-------+
-
| ID | Value |
-
+----+-------+
-
| 1 | Val1 |
-
| 2 | Val2 |
-
+----+-------+
-
-
Table: Data_Project2
-
+----+-------+
-
| ID | Value |
-
+----+-------+
-
| 1 | Val3 |
-
| 2 | Val4 |
-
+----+-------+
You would usually be much better of using something more like this:
-
Table: Project
-
+----+-----------+
-
| ID | Name |
-
+----+-----------+
-
| 1 | Project1 |
-
| 2 | Project2 |
-
+----+-----------+
-
-
Table: Data
-
+----+-----------+-------+
-
| ID | ProjectID | Value |
-
+----+-----------+-------+
-
| 1 | 1 | Val1 |
-
| 2 | 1 | Val2 |
-
| 3 | 2 | Val3 |
-
| 4 | 2 | Val4 |
-
+----+-----------+-------+
There you don't have to manipulate the tables themselves, just the data inside them, which is much easier to maintain (at least until you reach a massive database size).
Adding a new project becomes as simple as adding a new row to the Projects table, rather then create a entirely new table for it. And if you need to store additional data on the projects themselves, that can simply be added to the Projects table, whereas before you would have no way to add Project details, other then having them detaches somewhere in yet another table.