You could, but it's not necessary and storing the passwords in such a table is an avoidable security risk.
You can use the scripts listed under Accounts in the script editor to manage security accounts. In order for these scripts to work with a user that does not have full access, you can select the "run with full access privileges" option for these scripts.
I am not sure how the account script works without adding username and passcode fields.
I tried using the script but it wont let you leave it blank and when I add a username and passcode then use a button to access the script it says the name is taken. But when I added a user table and used fields username and passcode it worked fine.
How do you use the account script when trying to add new uaers without having a user table?
I didn't say to not have accounts and password fields. I indicated that you do not need to store the passwords. You can and probably should build a table of account names with info in other fields about each user's account. Use a global field for your passwords and clear this field when you are done.
Or if compiling to a runtime, simply follow this route:
- save a copy of the solution for a master file/backup
- take your solution and compile it to a runtime and be sure to check the Remove admin access from files permanantly checkbox
This will remove any ability for an end-user to modify any code or even enter layout mode.
Note:You can lock down a FMP solution or runtime solution.