Stopping Windows Close Button

[johnrh]

I am having a problem with corrupt files and have narrowed it down to the user closing the application via the windows X button (top right of screen) instead of using the quit button which closes all the files in an orderly manner.

I need a way to disable the window button at the top right forcing users to use the quit script.

the application will eventually run in runtime (developer) but I dont want to use Kiosk mode.

Any suggestions - others MUST have hit the same situation

Many thnaks

John

[cjaeger]

why not run a closing script which calls the actual close script in main database. (set it in preferences->document)

alternatively, you can run display message "please use close button ... or use a loop wit pause(1 sec)

[SteveB]

I'm not sure but I think Secure FM from New Millenium will enable you to remove the Windows Close (as well as specific menu items and whole menus).

Steve

[LaRetta]

Hi!

WindowUtility (by PracticeMaker) will also stop the closing of a window, using External("Wind-DisableWindowClose", "WindowName|Switch") and this particular function is cross-platform (some WindowUtility functions aren't).

URL is: http://www.practicemaker.com/

WindowUtility has been discussed on this Forum before and you might like to research those posts. It's obviously a great program, although I'm not sure it can be used in a runtime

Cheers!

LaRetta

[Lee Smith]

I agree with Christian,

Any multiple file solution should always have a closing script, along with an opening script too. In my opinion, any solution with more than one file that doesn't have a closing script indicates to me that the developer is either sloppy or lazy. In addition, a closing script should only close the set of files, not FileMaker. Nothing tees me off more than to have FileMaker close when I close a file.

my two cents worth

Lee

[Kundinger]

Hello John,

Your issues are not uncommon to customized systems. The key to this type of system is to 'think out' every possible user-scenario... meaning users tend to do the unexpected.

To solve the issue of 'improperly' closed files (force-quit, crash, close, quit, etc.), I have implemented 'opening' & 'closing' scripts to reset globals and to 'properly' open and close files.

I utilize a set of script steps in the 'closing' script that will check to see if the user is actually 'quiting' the system or if the user is trying to 'close' a specific file. If the user is 'legitimately' quiting the system (from a MainMenu file)... the MainMenu file will close all other files properly. If the user is 'improperly' closing files... the 'closing' script will 'alert' the user that they are attempting to perform an 'improper' operation. The user will then be given a few 'choices'... "Cancel"... to continue working; "Hide"... to hide the system; or, "Quit"... to quit the system.

The above ideas should be able to be integrated using built-in FileMaker capabilities and with minimal effort and minimal user 'confusion'.

I hope these ideas help. Feel free to contact me directly for further assistance. Good Luck!

Bob Kundinger

[email protected]

[Anatoli]

I've found that closing scripts are NOT executed if networked file is closed by Ctrl+W. FM5.5, W2k.