MacaroniDuck

Well, I can certainly see how it would be useful in certain situations. However, since Filemaker makes a big deal about it in their documentation, I wouldn't file this under "undocumented feature", but rather full-fledged bug. I realize that they can't control how browsers are built, but since they make such a big deal about security and being sure that users are logged off, they could have a) come up with a solution or : Emphatically stated that none of this will work without closing the browser. *shrug* Thankfully I almost never use IWP. This is a quick project for a client on a very small budget.

I should add that when I 'unhid' the status bar and used the built-in "logout" button, I still had the same result (i.e. the user wasn't really logged out) Note that setting the timeout down to a low amount like "1 minute" isn't a viable solution.

I've constructed a site using IWP in which the status bar is hidden and locked. I've added a "logout" button for the users with the "Exit Application" step attached. Unfortunately, it's not working. It appears to log them out and sends them back to the home page. However, when clicking the link to re-enter the application, it logs them in automatically. I'm guessing this has to do with the browsers caching the username/password. It's not really practical to get the users to flush their cache each time (or even close their web browser). Is there some other way around this? Note that I get the same results with both IE and Netscape.