VISUAL QUICKPRO GUIDE FileMaker Pro 7 Advanced FOR WINDOWS AND MACINTOSH [Electronic resources] نسخه متنی

اینجــــا یک کتابخانه دیجیتالی است

با بیش از 100000 منبع الکترونیکی رایگان به زبان فارسی ، عربی و انگلیسی

VISUAL QUICKPRO GUIDE FileMaker Pro 7 Advanced FOR WINDOWS AND MACINTOSH [Electronic resources] - نسخه متنی

Cynthia L. Baron, Daniel Peck

| نمايش فراداده ، افزودن یک نقد و بررسی
افزودن به کتابخانه شخصی
ارسال به دوستان
جستجو در متن کتاب
بیشتر
تنظیمات قلم

فونت

اندازه قلم

+ - پیش فرض

حالت نمایش

روز نیمروز شب
جستجو در لغت نامه
بیشتر
لیست موضوعات
توضیحات
افزودن یادداشت جدید











Disconnecting Inactive Users


If you're running IWP without FileMaker Server Advanced, you're limited to only five connections at a time. That limitation can make it pretty frustrating when a user logs into the database, then walks away for a cup of java and a chat with the person in the next cubicle. Even worse is when the user thinks that he has disconnected because he closes his browser, but hasn't clicked the log out button in the status area. FileMaker thinks that there is still a live connection. To address these frustrations, you can set a short idle time before the user is disconnected.

To restrict user idle time



1 .Choose Edit (FileMaker Pro in Mac OS X) > Sharing > Instant Web Publishing.

2 .In the Instant Web Publishing dialog box, click the Advanced Options Specify button.

3 .In the Session management section, set a time in minutes to disconnect an inactive user (Figure 17.27). Click OK twice to finish.

Figure 17.27. The more users who need to access your database, the shorter the idle time.


[View full size image]

Users are considered inactive if they shut the browser window without logging out, or if they fail to interact with the database in the Web browser.


Tips

IWP's status area contains a Log Out button. If you are building your own interface instead of using the status area, you can create a button and attach an End Application script to it. Be forewarned though: Neither LogOut nor the script will disconnect the user from the site. They only end the session on that specific database. The only way to completely release the connection is to close the browser window after logout. Be sure to get your users to close the browser window at the end of their session.

If you use up all your connections and you can't wait for the sessions to time out, the only way to clear the connections is to close the database file.


/ 227