My last article discussed the limitations of the built in Domino profile documents when used on the Web. I then showed you how to create global profile documents that hold preferences for an overall application or database and simulate the functionality of true Domino profile documents. This article will extend those techniques to allow you to create individual user profile documents by adding the ability for each user to select their own preferred calendar language in the Domino Web popup calendar application I introduced two articles back. Don't worry if you didn't read the first article on how to build the popup calendar, however if you want to follow along, you will need to have read the article immediately preceding this one.

Getting up to speed
For those who don't have my last article in front of them let me refresh your memories a little. We are working in a single database that now has three forms and two views. The most important forms are Calpop, which contains the code to draw the popup calendar, and CalPro, which is acting as a profile form that contains global database information on two or more languages available to the calendar, specifically the names of the supported languages and the names of the days and months in each language. Currently the database only allows one language to be used at a time and we control which one with a radio button field on the CalPro form.

User profile documents
Now let's create a simple form to hold each user's individual language selection. Create a new form called "UserPro". Create a computed-when-composed text field named "usr" and give it the formula value: @UserName. Beside the usr field create a field called "docid". The formula for this field should be: @Text(@DocumentUniqueID) and then create a last filed on this line called "SaveOptions".

FIGURE A


The SaveOptions field ensures only one document gets created per user. Roll over picture for a larger image.

SaveOptions is a reserved Domino field name that controls whether the field contents in an edited form will actually be saved when the save command is issued. If this field is set to "0" then no save occurs and no new document will be created. The formula for this field should be: