I was wondering if there was a way to send the information on the user registration page to a different table than the table that is used for login information? Lets say I have 2 tables, table 1 is "accounts_pending" and table 2 is "accounts_users". When someone registers, the data is sent to the "accounts_pending" table. Once an account is approved, the information is sent to the "accounts"users" table.
My reason for this is because every account has information stored on them in the "accounts_users" table, but not every account has a login to the website. When I was going to do was when I view the pending users in the separate table, I can select the account from the "accounts_users" table, and it will update that id number from that table with the information from the "accounts_pending" table. To give it more of a perspective, this is for a condo association where the board has an account under the "accounts_users" table with their name, contact information, account balance, etc. This is why every account doesn't have a login for it unless the co-owner wants to have access to the website. If they do decide to have access and create an account and its approved and put into the users table, they will have access to their balance and ability to update all their information that we have on them.
Or maybe someone else can think of a better way to create this setup or how to handle the situation like this?
My reason for this is because every account has information stored on them in the "accounts_users" table, but not every account has a login to the website. When I was going to do was when I view the pending users in the separate table, I can select the account from the "accounts_users" table, and it will update that id number from that table with the information from the "accounts_pending" table. To give it more of a perspective, this is for a condo association where the board has an account under the "accounts_users" table with their name, contact information, account balance, etc. This is why every account doesn't have a login for it unless the co-owner wants to have access to the website. If they do decide to have access and create an account and its approved and put into the users table, they will have access to their balance and ability to update all their information that we have on them.
Or maybe someone else can think of a better way to create this setup or how to handle the situation like this?