you should not use 2 tables for this. you should use only one table and set up user levels
using 2 tables will create unneeded confusion, and complexity to your project and lead to unwanted bugs.
well – it’s not too clear?
checkbox be selected as well?
When creating the Administrative pages, the checkbox option to include the delete button should be checked so that the admin can delete users if needed.
when creating the public pages, the checkbox to include the delete button should not be checked, you don't want users to be able to delete records, right?
should have access only to the profile page. But I have
access to admin_results, admin_insert – these are all pages
with restricted access to admin login and not members
this is the sort of issue that will happen as a result of using 2 tables. this is exactly why i suggested at the very beginning that you don't use 2 tables and only use 1.
most likely the 2 tables use the same column name for the user group column or the ID column which will cause the session being saved on login to be the same, thereby making it impossible for the system to determine if a user or admin has logged in. This is why using 2 tables is a bad idea.
instead, use 1 table, and use user level authentication which uses the UserGroup column to determine which user type is logged in.
wouldn’t it include the users/staff as well in the results
page – this is not what I want – I only want to see
you can set the results recordset to include a where clause to return only members/customers based on the UserGroup column value.