Warning: count(): Parameter must be an array or an object that implements Countable in /customers/2/8/1/bizzybee.be/httpd.www/wp-includes/post-template.php on line 251 Warning: count(): Parameter must be an array or an object that implements Countable in /customers/2/8/1/bizzybee.be/httpd.www/wp-includes/post-template.php on line 251 Warning: count(): Parameter must be an array or an object that implements Countable in /customers/2/8/1/bizzybee.be/httpd.www/wp-includes/post-template.php on line 251 Warning: count(): Parameter must be an array or an object that implements Countable in /customers/2/8/1/bizzybee.be/httpd.www/wp-includes/post-template.php on line 251

Prohibit design refresh Reporter

I needed some way of listing all design elements that have the property “Prohibit design refresh or replace to modify” enabled. Instead of doing this manually, I created a little agent that does this for me.

So I tweaked it a little and wrapped it in a little database to share it with you. Little tools like this you don’t need every day, but they can be handy every now and then.

Prohibit design refresh or replace Reporter

How to use?

  1. Copy/paste the form, view and agent ProhibitReport to your target database.
  2. Don’t change the names! This way the agent can exclude those design elements in its report.
  3. Run the agent from the menu Actions – ProhibitReport.
  4. Wait some seconds…

What’s next?

I don’t know yet. The tool opened a little window in my head that makes me want to create more extended reports for designers. I have some vague fluffy idea clouds about what those reports could contain, but your comments can help me outlining them more.

Or you could just say: “Naaah, rubbish!” :-)


  1. Cool idea. I think something like this would fair well on OpenNTF as a utility that would allow you to search all databases, or choice databases or whatever for design element reports.


  2. Hi Keith, thanks! Indeed, maybe this could be a new utility, but I think the tool should do more then than just showing “prohibit…”.
    Btw nice website!

  3. Thanks Martin, ditto for yours, dunno how this UI jewel got past me for so long :)

    But I agree about the utility, it should definitely do more than just find the “prohibit…” items. I’ve never tried to interact programmatically (sp?) with design element properties but I find the thought of it intriguing none the less.

    Keep the ideas rolling and the creative honey pouring ;)

  4. Thanks, but it’s easy how it got past you: I’m only really blogging since October 2007 :-).
    It would be nice to see all dependencies of a database listed…

  5. Actually, getting the ‘Prohibit’ information is a subset of what you get from the Dependencies tool in NotesHound.

  6. Ken,
    I looked at NotesHound; it could be worth the money, but it’s not cheap. Maybe a trial version would help?

  7. ‘Cheap’ is a relative term. Compared to what you need to pay for similar tools from other vendors, NotesHound is cheap. In particular when you consider that the license cost is a on-off, you get free upgrades forever.

    When NotesHound was a pure Notes Client set of tools, we did have trial versions. At the moment we don’t – but we are seriously considering that option. Our problem is to keep the codebases in order without too much of a hassle.

  8. I know cheap is relative. My first impression was: “wow, it does seem to do great things that I could use!”, followed by “where’s the trial?” Investing in software is important, but putting money in the wrong tools is a shame. I don’t say your software is not good, I simply don’t know, I’d like to play with it.

  9. Hi again Martin,

    Just to let you know, you can now get trial versions of Noteshound.
    If you want one, just go to our website (http://www.noteshound.com), hit the ‘Trial’ button, fill in and submit the form.
    Once submitted, you will be sent a link to a trial version that won’t expire for at least a month.


  10. Dear Martin,

    very good idea, but two suggestions:
    1. There are three elements where the Prohibit design Refresh Flag is set in another way than typically:
    – The database icon
    – The HelpAbout Document
    – The HelpUsingDatabase Document
    In these cases you must check, whether the $FLAGS not has an “R”, in all other cases if the $FLAGS has a “P”

    2. In some cases you must make the search reverse: is it guaranteed, that the “P” is set ? These are common Folders, especially in the mail file.

    If a database resides on a template the “P”-Flag is automatically added to each element you add to the database. If the database has no template inheritance it is omitted.

    If a mail user disables design inheritance for some time all folders he creates during this period will miss the “P” flag – and will be deleted with the next design refresh after he (or his administrator) enters an inheritance again. Loss of folders can be a great pain to users who organize documents this way.

    Kind regards



Leave a Reply to Martin Vereecken Cancel reply

Your email address will not be published. Required fields are marked *

Warning: Use of undefined constant AUTH_KEY - assumed 'AUTH_KEY' (this will throw an Error in a future version of PHP) in /customers/2/8/1/bizzybee.be/httpd.www/wp-content/plugins/wp-math-captcha/includes/class-core.php on line 713 57 − 51 =

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>