innodes Posted September 7, 2007 Posted September 7, 2007 Is there a way to disable the window exit (upper right corner of window frame "X" on windows or the left red button on a mac) function. I would like a clean bar on the top of the window (with text is ok) and force the user to use the buttons that are built into the Filemaker database as opposed to just killing the window.
Ted S Posted September 7, 2007 Posted September 7, 2007 Mac I don't know about but on Windows I'm pretty sure you can't do anything to prevent the user from closing the application this way.
LaRetta Posted September 7, 2007 Posted September 7, 2007 (edited) If you're willing to go plugin, you might check out Window Utility and Secure FM. Both allow disabling and removing windows X from windows (among other things). Here's the links: Window Utility Secure FM Edited September 7, 2007 by Guest
aholtzapfel Posted September 9, 2007 Posted September 9, 2007 I've heard but never done this, Can't you Wrap filemaker with a anouther app, or even a vbs script, capture the close event and prevent it. This is a little beyond me, but I swear I came across that somewhere.
Vaughan Posted September 9, 2007 Posted September 9, 2007 Try this -- on a copy of the file: Set a shutdown script to open a new window of the file.
innodes Posted September 10, 2007 Author Posted September 10, 2007 thanks all, LaRetta, Plugins aren't allowed within our security yet. Good idea, but I'm locked out of this one. aholtzapfel, Thanks, I'll look more on this, and hope someone that is familiar with this chimes in. As for vbs, the problem there is I have mac users on the network as well, and I have heard that vbs will not work under mac. Vaugh, Sounds interesting, but I am not quite following. Could you please elaborate? thanks, mike
aholtzapfel Posted September 10, 2007 Posted September 10, 2007 Try this -- on a copy of the file: Set a shutdown script to open a new window of the file. WOW! Kind of neat! if the file is closed it does pop-up a new window, if filemaker is closed... it throws the whole thing into an infinite loop, continually opening windows, then closing them. I don't see a way around the the infinite loop. (could really be useful if there was)
Vaughan Posted September 10, 2007 Posted September 10, 2007 Oh, there is a way around the loop if you think about it. It could be as easy as setting a global variable (or field) and checking the value of the variable (or field) before creating the new window.
Asda Posted September 13, 2007 Posted September 13, 2007 Try this file, I got it from these forums but cannot remember who the original poster was. WindowandToolbarControl.zip
Lee Smith Posted September 13, 2007 Posted September 13, 2007 From here. It might be helpful to read the whole Thread. Lee
innodes Posted November 16, 2010 Author Posted November 16, 2010 The answer I had gone with was a method that used a loop to lock the windows. It was working. It has been a few years, and some of the locks seem to now be broken. I don't know why or what changed. So I came back to the forum. The link above does lock a window, but I can't figure out how the "my close" script is tied to the window's close command. Any help is appreciated. I went to the link of the post, but still don't see it.
innodes Posted November 17, 2010 Author Posted November 17, 2010 Did some more digging and found the following post on how to do this in windows. here This is the method I was using, found the breaks and it is locked again. Thanks forum. I would still like to know how to do the scripted version mentioned above if anyone knows.
Recommended Posts
This topic is 5121 days old. Please don't post here. Open a new topic instead.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now