Imagine you have a FileMaker database that's configured to login using the guest account.
Now create an admin account and reduce guest privileges to read-only.
Now you're locked out of the database. It won't ask for a un/pw because it's configured to login using the guest account. You can't change the settings because you don't have access privileges.
Wow. What a rotten piece of junk.
Fortunately I'm geeky enough to try starting up holding down the option key. As I'd guessed, that forces FM to ask for a un/pw despite the startup setting.
Update: If you change the startup account you do get a warning about login (shift for windows, option for Mac), but you don't get this warning if you reduce privileges for an existing guest account.
Update: Now that I've calmed down, here's what FileMaker could do to fix this:
- Include a menu option in a logical place for requesting a change in privileges/login.
- If the structure of FM is such that this cannot occur without a restart, then FM should provide a dialog saying (in essence) 'Close and restart required, is that ok?'