On an Insert form, I have users entering usernames/passwords and much of usual stuff on a main table. (address, contact info, etc,) Also I have two more connecting forms on a pg 2 Insert, and pg 3 Insert.
But considering the possibility of having to (a) echo the usernames/passwords, along with idea of echoing the other two tables into yet others, combined with the fact that checking unique col. field values for the creation any new user passwords will be needed at all times -- I can see where my main table should remain intact as a production table. Usernames and passwords can only remain in a single table, right? (If access to other user tables are restricted by these)
Is there an alternative -- users are doing Inserts without restricted access whatsoever at this point; no usernames, no passords, no access levels are required for Insert into this first main table. Kind of a scary thought.
Also, considering that registered users will be performing updates on these same initial table columns on their usernames & passwords/other info. with their entry restricted by username/password/access level. Yet nobone else can update unless they have these values. They can only do Inserts.
This can't be the optimal structure. If the table is needed to maintain only for usernames/passwords, should it become permanent?
Would appreciate any recommendations.
