If the users are to create their own account, that would mean that you have some fields where the user enters an account name and password. At the time they do this, you can update a table of account names and add the new account name to this table before creating the new account. Set up a unique values validation on the account name field in this table and the user will get an error message.
And a script can trap for the error if you want to script it.
Say the user enters a new account name into a global field: Globals::gAccountName
The script might work like this:
Go to Layout ["Accounts" (Accounts) ]
Set Field [ Accounts::AccountName ; Globlas::gAccountName ]
Set Error Capture [on]
Commit recordsIf [ Get ( LastError ) > 0 ]
Show Custom Dialog [Globals::gAccountName & " is already in use. Please enter a different account name" ]
Thank you for responding. Yes, I am aware of (and do have) a table of logins. I was hoping to find a way in FM to check against the actual accounts under FM security. Cheers.
That is similar to the old way I used to do this. I created a user record. Not anymore. The fields that are set are all globals. Thanks for responding.