Thanks for posting.
I've tried multiple times but haven't been able to reproduce the issue in a similar Windows 2008/multiple browser configuration. I'm trying a really basic test; please let me know a better way to simulate an environment closer to your issue or if I am missing any steps:
- In my database, I'm launching the following script step via File Options > Perform Script so that the status bar will be locked when the database is open:
Show /Hide Status Area [Lock;Toggle]
- I have a button on my layout that executes Exit Application
- I'm hosting via FileMaker Server 11 Advanced v2 and accessing my database through IWP
- To log out, I click the Exit Application button
Hi Donald Clark,
I sent you a private message through the forum. To check this, click on the Inbox link in the upper right corner of the forum.
Was there a solution to this?
My logout button was working fine in IWP, then unexpectedly started going to a different layout instead of exiting the application.
My config - Filemaker Pro on Wondows Server 2008, tried on Safari, firefox, chrome and IE with the same result.
Hi Phil Hanson9463,
Thanks for posting.
At this time, there is not a set resolution for the thread starter's issue.
However, I do not want to immediately lump your experience with the issue described above. While the thread starter had an issue with hiding the status bar/logging out of the file, the button in your file is going to another layout.
Try taking the file offline and running File > Recover on it. Does the file come back normal?
Also, how many times will the button take you to a different layout? Every time? One out of every 5 times? Once you get a benchmark, create a test file and add a similar button/exit application script (create a new script). Do you exit the application successfully every time or do you experience a similar behavior with benchmarks that rival the original file?
Hi tsturtle and thanks for your interest. Sorry for the delay, I was away for a couple of days.
I recovered the file and the message was that no errors were found on the file and it was ok to use.I think I found the problem;
I had a closing script redirecting to that layout.