Archive for the ‘Best Practices’ Category

Frame design Best Practices Part II

Monday, June 9th, 2008

Extending on my previous article on Frame design Best Practices I have found something else worth mentioning that is not written in any designer help.

When trying to open the preview pane within a 3rd party application today I got presented with an error message: “Cannot execute the specified command.” (more…)

Doclink does not open with LS created Doclink

Friday, September 14th, 2007

Today I had an interesting issue I definitely need to put out here to be able to remember it in the future.

I used a piece of code (see below) to append a link to a document, sent out via an email message to another user. When the recipient opened that message and clicked the doclink a dialogue box came up “The Doclink database cannot be located.” asking the user to select the server where the linked database is located. This issue however did only happen in some circumstances. (more…)

Name Field Maintenance Part II (Development)

Friday, June 29th, 2007

This is the follow up to my last entry with regards to name fields in Lotus Notes/Domino applications. While Part I had been focused on the Administration side I am now continuing with the Development aspects.

When developing a Lotus application the first question would be whether name fields will be required at all and if so what kinds of fields are required. If it is decided that no name fields are required I would still suggest following my other comment regarding the prevention of the use of the $Readers field.

(more…)

Frame design Best Practices

Monday, June 25th, 2007

Today I learned about an interesting Lotus Notes design feature, which is definitely eligible to be shared (of course) and placed to the Development Best Practices list.

The current application I am coding does make use of three frames within a frame set to have it appearing more professional then the standard R5 View Navigator. Until today I did never bother about any naming conventions of these frames. One had to be the header, the left one the navigation and the right one the mainframe.

But: if you don’t want your application falling back to the ugly view navigator on the left hand side when somebody is opening a view link or tries to open a view from the View -> Goto Menu it is important to have at least one frame named “NotesView”. This frame is obviously internally used to define the main frame of the application and with it the target of each undefined view or document link.

The information I found at IBM related to this issue is related to version R5 of Lotus Notes. I am not 100 percent sure whether this still applies for version 7 but I successfully tested it in version 6.5 today.

(more…)

Name Field Maintenance Part I (Administration)

Friday, June 22nd, 2007

Names can (and will) alter. There are marriages, divorces, organisational changed or changes in the hierarchy of an user name. Each change requires individual action to maintain these names for each individual document, each database on all possible server. Sounds like a tedious task?

This article describes some of the settings to be considered from the Administration (Part I) as well as best practices from the Development (Part II) perspective when working with name fields in Lotus Notes/Lotus Domino applications.

(more…)


Creative Commons Attribution-NonCommercial 3.0 Unported
This work by cubetoon is licensed under a Creative Commons Attribution-NonCommercial 3.0 Unported.