Hello,
How can I customize the toolbar for my database (I want to remove the save button on the toolbar when the user open the database)? Or is it possible to disable the remove button?
Thanks in advance.
Subject: Customized Toolbar
… Or is it possible to disable the remove button?
Sorry I meant: …disable the save button.
Sorry for the typo.
Subject: RE: Customized Toolbar
“I want to remove the save button on the toolbar when the user open the database)”
Why? What are you trying to prevent? And what makes you think that hiding the Save toolbar button will prevent the user from using the File > Save command, Ctrl+S, followed by Yes, etc?
As of R6, the Save toolbar button will only be active when a document opened into edit mode has the focus. If the user can’t put a document into edit mode in the first place, they won’t be able to make any changes to save. If you want to prevent unauthorized editing, hiding the Save button won’t prevent the user from saving the document using any of the other above-listed methods; instead, you should use normal domino security mechanisms (ACL, Authors fields, etc) to control that access.
If it’s important that a user be able to put a document into edit mode, but the point of the form is not to create a document (For example, in a dialog box being used for interactive calculations.), then using (a) a SaveOptions field to prevent the do-you-wanna-save-this-dirty-document prompt and (b) continue = false in the QuerySave event to cancel explicit attempts to save will take care of it.
Does that help?
Subject: RE: Customized Toolbar
Yes you are right, I am trying to prevent the users to use the save buttton on the toolbar.The problem is:
I have developed a big workflow app which is used by 70 departments in my company. The app has its save button which has some @If commands to check if the user comes from the right departments or not (the right department (which consists of 2-3 persons) can modify the the form).
But unfortunately, a user has use the save button to bypass the security check. We have discussed it and as conclusion, the best way to prevent it is making the customized toolbar for the database. When possible, the toolbar should be disabled, so that the user use only our developed buttons.
Do you have any idea how to do it?
Or perhaps do have other solution than removing the toolbar (preventing the user to bypass our own save button)?
Thanks in advance.
Subject: So you are asking the popular question: How do I force users to save by clicking my save button only?
This can certainly be done, and it’s not difficult; you will find plenty of postings on how to do this if you search both forums for key terms like “force and save and button”. However, the best advice by far is not to do this. Don’t write hard-to-maintain code that defeats many of the fundamental features of the Notes client. Not only are you spitting into the wind – working really hard to defeat normal behavior instead of working with it – but you’re frustrating and confusing your users, who are used to being able to use the Notes client in certain ways, and don’t appreciate it or understand why when sometimes the client doesn’t behave the way they expect.
If there are certain things that need to be processed when a user saves, then using the intended mechanisms for doing this (QuerySave and/or PostSave and/or Computed fields with @isdocbeingsaved, @isvalid, Compute after validation, etc) will be a lot less work, a lot less confusing, and a lot more flexible and friendly for the developer, the maintenance coder, and the user.
Subject: RE: So you are asking the popular question: How do I force users to save by clicking my save button only?
Amen to that. QuerySave and PostSave should make the “you must save with this button” strategy a complete loser.