Hi FileMaker Folks -

Continuing to explore FMPro8, I published a quick and dirty flat file to
the Web using IWP. I want to collect some records, controlling user
actions with web-compatible buttons. My login is defaulted to Guest and
the privelege set is Entry Only. Nearly everything seems to work okay.
I can log in with Safari under Localhost, and my "New Record" button
works fine. However, I cannot seem to script a "Logout When Finished"
button. I've tried several likely-looking steps including Exit
Application (which I thought was a little extreme but it says it's web
compatible) and no joy. My logout script commits the new record okay,
but continues to display it (I would rather it did not). When I exit
Safari and try to close my database file, FMPro says Guest is still
logged in. If I access the database again by reopening Safari, it says
Guest is logged in twice! Obviously this is going to cause a problem.
There is a Logout button on the status area you can display in IWP, but
I'd rather not show the user all those controls. How to log out by script?

Many thanks in advance for your continued kind assistance -
James

Interestingly enough, while FM7&8 are happy enough to show you the IWP home
page in situations where you *don't* want to show it (for example, when
timing out of a session), there is no way to return you there when you
*want* to go there. If you link to the IWP home page in a button, for
example, it will open up in a new window.

There is also the limitation in that FileMaker will not close the current
browser window. (It may not be able to do this because of JavaScript
security limitations.)

The best workaround I can suggest is that you take the user to a "You've
Logged Out" page which signals the end of their session but does not
otherwise provide a mechanism for them to return to the database.

Bill

"James" <jbusch (AT) pixi (DOT) com> wrote

Bill Marriott wrote:

And many thanks for your quick response. I'm sure your suggestion will
solve the issue of the newly created record still being displayed, but I
wonder if, after five people have logged in and out, FMPro will believe
that the five concurrent session limit has been reached. Would the
database have to be closed and relaunched? That's the problem I
referred to above, and it would certainly mess up my plans. I guess I
will find out when I test it hosted, and perhaps I will have to show
that complex status area after all, just so people can log out.

Thanks very much again -
James

For that side of things, perhaps it would work if, after you take them to
the blank layout, you use the "Relogin" script command to force a log in
with an invalid username and password?

Bill

"James" <jbusch (AT) pixi (DOT) com> wrote

Bill Marriott wrote:

I tried that script step, but without the invalid login. I'll check it out.

Thanks again -
James