Q
Problem solve Get help with specific problems with your technologies, process and projects.

How can I set a date for a client to no longer open or run?

As part of my company's sales presentation, we offer a demo of some of the Notes databases we've created to prospective clients. Is there a way to set up the Notes client so that after a certain number of days (we're thinking 90), the client ceases to open/run? I have explored an ID that expires fairly quickly, but am not happy with the results. Do you have any suggestions you could offer me?
The whole client? Or just your databases?

If you want a Notes client to stop operating, I guess the easiest way to do this would be to write an agent in the address book template that checks to see if the creation date (maybe of a profile document, created upon database open) is more than 90 days old. If the profile date is more than 90 days old, then close the Notes client with @Command([ExitNotes]).

You won't, of course, be able to stop a "power" user from reconfiguring the Notes client to get around this.

A more effective way to do this and a way that may provide a better option for you and your clients might be the following option, which just locks down your demo databases.

  1. Set the ACL of the database to have default "Manager" access.
  2. Remove all other ACL entries (LDS, LDS, ODS, etc.).
  3. Create a generic profile form in the database with a "CheckDate" field.
  4. Write a database script, which in the initialize event of the DB checks to see whether a corresponding profile document exists; if it doesn't, create it and write to the CheckDate.
  5. Once you have a handle on the profile document, check the "CheckDate."
  6. If the "CheckDate" is more than 90 days old, change all the ACL entries to "Reader" (in case the demo tester has modified the ACL).
  7. Hide the design of the database.
By doing this, you will basically create a time-out for your database, where the application will be fully functional for 90 days, and after that period the user will be able to review and play in the database, but will not be able to edit or create any new information. In other words, they can still review the functionality, but will have to come back to you to continue using the application.

Dig Deeper on Lotus Notes Domino Administration Tools

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

Start the conversation

Send me notifications when other members comment.

Please create a username to comment.

-ADS BY GOOGLE

SearchWindowsServer

Search400

  • iSeries tutorials

    Search400.com's tutorials provide in-depth information on the iSeries. Our iSeries tutorials address areas you need to know about...

  • V6R1 upgrade planning checklist

    When upgrading to V6R1, make sure your software will be supported, your programs will function and the correct PTFs have been ...

  • Connecting multiple iSeries systems through DDM

    Working with databases over multiple iSeries systems can be simple when remotely connecting logical partitions with distributed ...

SearchDataCenter

SearchContentManagement

Close