Ditto, Joel's comment. I love the fact that dialogs work in Web Direct. They were not available in IWP. Logins may not be the only time you need this "hidden display", so use the dialog option when desired.
And ditto, Bev's comment :-)
Another really nice thing about custom dialogs in WebDirect is that buttons will stretch (widen) to fit their text!
Also, long Messages are scrollable(!), although if Mac scrollbars are hidden (at OS level), then users likely won't know there's more to see.
(bonus points for anyone that recognizes the text in the Message in the screenshot ;-)
The text is from War and Piece... Thank's to Google .
Could you share details of how you did this?
1 of 1 people found this helpful
The main idea is that the user gets greeted with a custom dialog with two fields: username & password. When they click the dialog's "Log in" button, FileMaker does a search in a "users" table for an exact match of both fields (exact so that "joe" won't also find "joel", etc.) If a match is found, then you let the person continue into the database. If no match is found, you give them other chances to log in. If they can't log in successfully, they can't get any further into the database.
In my situation, there were some WebDirect users who had real accounts (in the database or in ActiveDirectory) and some who only had records in the "users" table, so I had to first present everyone with the standard WebDirect login. The people without a real account were told they need to first select "Guest Account" and then they'd get the custom dialog. If none of your users will have real accounts and all will just have records in the database, then you can skip this step and allow only Guest access to WebDirect.
I'm not able to put a copy of my file up as a sample, but here are screenshots of the key parts:
Since I'm allowing regular-account logins as well as user-record logins, my "opening script" (set as OnFirstWindowOpen script trigger) runs the custom-dialog login script ("Login_Non-ActiveDirectory") as a subscript. If you don't need this step, you could put the login script as part of the opening script.
Here's the main script:
(note: my "users" table is actually called "Coach")
Also, I recommend that you set the password field to be stored as Unicode so that it is case-sensitive (normal FileMaker finds disregard upper/lower case)
Hope that's helpful.
: database design
: web development
Thanks much! I'll be giving this a go in the next several days, hopefully