Two things to check:
Open file options and see if the file has been set to automatically open with an account name and password.
Open Manage | Accounts & Privileges and check to see what account names and passwords have been specified.
The file options dialogue is set to login using an account name and password (Account listed as "Admin"). Also, the Perform Script option is checked with the script "Open Script" specified, though I'm not sure why that is.
The Accounts and Privileges shows two accounts: Mine (my name) and Guest. Clicking on my account shows my name as the Account Name and the password that I originally set. The Account Status is set to 'Active.'
The only things that have changed recently on my computer were the addition of recent Mac system updates and there is a Microsoft Office 2004 XML update waiting to install next time I restart. However, something else I've noticed is that the FMP Help file no longer loads or runs.....
What do you think?
Well it seems we've found the explanation for one part:
"Over the last 2-3 days I've noticed that I can launch the patient info database from the desktop alias without it requesting a password. The other protected dbase continues to function as it always has and will not launch without a password."
You've indicated "The file options dialogue is set to login using an account name and password "
That might indicate why the file opens without asking for a password. Clear the "log in using" check box and then close and re-open your files. You should now see a request for a password when you open the file.
No go on that Phil.
Clearing the "log in using" checkbox does not affect the problem. Even resetting that checkbox with my account and password has no effect. Anyone double-clicking that desktop alias can open the file.
The only other wrinkle I can think of is that I use the Mac OSX Keychain. It's highly unlikely, but I may have inadvertently checked the box "Remember this password in my keychain." However, the only entry for FMP in my keychain is a secure note, which wouldn't automatically give up the info within just by opening the database alias.
Does it matter if the 2 protected databases share the same account name and password?
(They always have and functioned independently.)
The one factor there is that if a script or data reference opens the second file, filemaker will automatically open the second file with the same account name and password as the first file. Thus, you won't see a request for a password for the second file under those circumstances.
The two secured files are totally separate. The one in question (client information) draws from the open-access file containing information about referring doctors. However, neither has any relationship to the third (secure) file.
The biggest mystery is that -- other than adding more records to each file -- I have made no changes to the structure of any of the files.