Stuart Taylor Posted February 24, 2009 Share Posted February 24, 2009 Hello, I have a data separation situation in relation to Start up / Login I have a GUI file on the local system and the Data file on the server. If an administrator changes the password for an account in the Data file the user can login to the GUI file successfully but when the GUI file then switches to a layout that calls on information in the Data file the authentication will fail and the file displays the FileMaker login prompt for the Data file. I want to avoid this. How can i test for the validity of the GUI accountname and password in the Data file without it failing and displaying the FileMaker login prompt for the Data file. I would like this to return an error for me to test and prompt for the user to change there password or try logging in again. Best Stuart Link to comment Share on other sites More sharing options...
IdealData Posted February 25, 2009 Share Posted February 25, 2009 I don't know of a way to error trap a file before you have it opened correctly. Shouldn't the ADMINISTRATOR be a little more responsible and make the password changes in both files? You could, of course hand password change/control to users with scripting. A combination of $vars and the Reset Account Password should do the trick. Link to comment Share on other sites More sharing options...
Recommended Posts
This topic is 5547 days old. Please don't post here. Open a new topic instead.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now