Hi, is there any way to bypass IWP user login window? Meaning that it will open the database based on the user on "File option, logon using".

The reason why I want to bypass it is... it will save the user from entering their username and password twice.

On our database we allow users to only access their own record. On my initial screen, they will enter their Member ID, Password and Birthdate (all fields input), then they click logon button that triggers a script to direct them on their own record (status bar locked) and no way for them to browse other records.

Any ideas?

Garry

Why not just use the initial login screen together with a startup script to direct them to the appropriate record. Then they won't need an extra screen. This is probably much more secure than having them enter a password into a field in IWP, since you can't mask passwords in fields.

Dana

Thanks for the suggestion, but this will give us much work to create password on each related file. I'm using "Show Custom Dialog" as a login window which allow me to mask the password into *.

Have you tested this using IWP? Show custom dialog is not supported under IWP...

If you have related files, you can use scripts within FMP to synchronize account information across files. What I opted to do was just put all the information that people would need into one file with many tables so that the accounts could be centralized.

uhoh... i didn't know that Show Custom dialog not supported under IWP, thanks for the info. Have you ever written an account synchronization script? I appreciate if you could share it. Its too late for me to convert my related files into tables coz i've got some scripts stored in each file.

I haven't done this myself, but here is a post that shows how it can be done:

http://www.fmforums.com/forum/showtopic.php?tid/112882

you will likely have to to the account creation and synchronization from a FMP client, but once the script is run, all the target files will have the same accounts and passwords.

Good Luck,

Dana

(Also, for consolidating into one file, you can import scripts from one file to another. You maybe already knew this, but just in case...)

Thanks Dana, I think the 1 file with multiple table approach is a good solution but is it also possible in FM7 to import fields from an external file into a table? since I got multiple fields on some external files.