Disable Program Close Button

[perryc]

Is there a way to hide or disable, not the form close button, but the MS Access close button?? See attached image.

Thank you in advance.

[pbaldy]

I've never bothered but:

https://www.fmsinc.com/microsoftacce...eventclose.asp

[isladogs]

Another method would be to remove the application window completely which removes the title bar, ribbon, quick access toolbar and navigation pane.
This leaves you with forms 'floating' on the desktop. See http://www.mendipdatasystems.co.uk/c...ace/4594365418

[perryc]

Ty both!!

Another question, if user use Control-Alt-Delete to quit an application, I am fine with that, but, can a certain code be executed prior to access closing? Just wondering.

[Micron]

If you remove the db close button, no doubt you'd provide a command button instead? You can run any code in its click event. I would not promote the idea of keyboard key combinations to close the db. You might want to consider a hidden form that has close event code, which I think is about the only way to deal with the possibility that users might find inventive ways to close the db that you don't expect.

[isladogs]

Whilst you can run any code you want prior to an orderly shut down, if you use ctrl alt del, all of that code will be bypassed.
As Micron has already said, make sure you provide a shut down button which cannot be bypassed.
If necessary disable the three fingered salute...but this requires a registry hack.
Don't forget other key combinations that shut down Access such as Alt+ F4

[Micron]

People would actually employ this method and close all apps and potentially sign off rather than perform orderly closing? I'd be logging them in anyway, so if I thought that might be the case, I'd check if they're already logged in on startup. If so, they had an abnormal shutdown and after logging a few of those I'd be ragging on them - at least.
To disable the key combination would mean a basic Windows functionality is removed - a sure fire complaint generator, assuming anyone needed to ever use it.

[perryc]

TY all for the replies. I see your point. No, I was just wondering if there is a way whenever access shut off, I log someone off. (currently, I have all the above in place, i.e. disable Window Close X, a close button that will change a value to indicate someone is log off...) the only problem I can not prevent is, when the database got frozen, sometimes due to network issues, someone will have to use the Ctrl-Alt-Del to exit. Then, it messes up the log to track who is currently log-in. Well, this does not happen often, so, I don't have to worry, I guess.

[Micron]

Is this db split and does the fe reside on a server and the fe on each user's pc? On one hand it sounds like it's not split, but on the other hand, you seem to be concerned about a db that everyone would have lost a connection to, thus likely you couldn't tell who's in and who's not because you would have lost connection also. Unless you needed exclusive access to the be (back end) I'm not sure I get why it would matter who didn't log out if it was split. You'd be able to gain access anyway, so it's a bit of a conundrum.

[perryc]

Micron, ty so much for your help. Yes, it is a split one, FE in local machines; BE in the server. The reason why I would like this is that I tried to monitor who had use the database and how long they had been using it. No worry, this is not a big deal.