Using one template for three different uses (Page 2)

Search DominoPower's 11,408 Lotus-related article archive

Home
EasyPrint
News details

Articles-only

Twitter Feed

Using one template for three different uses (continued)


DB := @LeftBack(@UpperCase(@Subset(@DbName; -1)); ".NSF");

group := @Trim(@RightBack(DB; "QADISC"));



S := "555-1111";

H := "555-2222";

D := "555-3333";



@If(group = "S"; S;

group = "H"; H;

group = "D"; D;

"")

Let's break down the code in segments. First, you'll need to figure out which database group you're working with. Set a temp variable, DB, to be the filename name, minus the ".nsf" extension. Note that you have set the filename to uppercase. This is done so that this database may be named "qadiscs.nsf" or "QADISCS.NSF" or any case combination, and the code will still work properly. Here's the code to make the name uppercase:


DB := @LeftBack(@UpperCase(@Subset(@DbName; -1)); ".NSF");

Then set a temp variable, group, to be the group name, which is really the filename stripped of the common characters, "QADISC". Given that you set the filename to uppercase in the last line of code, this text needs to be uppercase as well.


group := @Trim(@RightBack(DB; "QADISC"));

Next, you'll need to account for each group within QA, so let's set some temp variables for each contact phone number:


S := "555-1111";

H := "555-2222";

D := "555-3333";

From there, simply match the group with the contact phone number:


@If(group = "S"; S;

group = "H"; H;

group = "D"; D;

"")

This code or a similar variation can be used for a variety other functions, like formatting sequential number fields, in computed subforms, or behind buttons to load up a specific form depending upon the database (or group) name.

Why do it this way?
The main advantage to using one template instead of three would be maintenance. Should the customer come back with sweeping design changes, it would be easier to configure and maintain one template, rather than three flavors of the same basic design. Also, the code and naming convention are rather easy to understand and use; there's no rocket science here. The keys to using this technique are planning the design given the audience it is to serve and being sure to document where this code was used in the design. With proper documentation it would be a simple task to add support for another group -- say "Web Quality Assurance" -- from this template.

Chris Brown is a Notes Developer currently based in the Washington, DC Metro Area. Due to her rather common name, Chris is better known as her alias, Green Jellybean, which is the nickname for her green Toyota RAV4. She can be contacted at green_jellybean@bookideas.com.