I see were you guys pointing... But I think this is too much trouble because the app has a different target. This is for companies to test either their employees, either people applying for jobs. Therefore, most likely a user will enter the app only once. There are 90% chances that a user account would be used only 1 time, then deleted. So, storring all than in another table (although linked) would cause more trouble that it is supposed to sort.
Not to mention that this is using mySQL which anyway forbide me to use inner joins or stored proc. 
(But there are Access and SQL Server versions of the app - now I design all my apps with 3 diferent backends dbs).
Topic Options
Post Options
Thanks(0)
I must admit that my first thought was indeed to create a new table, but I thought that would add up redundant informations (we are talking here of thousands of students with 3-5 testes at least for each of them, so about 100.000 duplicate records. How could that be less resource consuming and efective then 3 lines of code?
