Search DominoPower's 11,323 Lotus-related article archive 
Home
EasyPrint
News details Click here for the RSS feed's XML code. This is not a browser URL.
Articles-only Click here for the RSS feed's XML code. This is not a browser URL.
Twitter Feed Click here for the Twitter feed.
PROGRAMMING POWER
How to audit your address book: more code
By Mick Moignard

Now we start the actual checks. If you haven't already read part one of this article, elsewhere in this issue of DominoPower, you should do so now. If you've mastered the code in part one, then let's move on.

First we check the Fullname field (this is the Person record field called User Name on the form) which allows all the different names and nicknames to be specified. When a new person is registered in Notes, the registration process adds the canonical format of the name as the first entry. It's displayed as abbreviated, but if what's stored is not actually the canonical form, then things will go wrong down the line, for example, type-ahead's name resolution as described in Knowledgebase item 180944. The second fullname entry is set to the common name. As we will see, it actually doesn't matter where in the list the common name form appears.

'1 check that the Fullname (username) 1st value is the canonical name and

If Lcase(pers.fullname(0)) <> Lcase(realfullname.canonical) Then
Call reportdocbody.addtab(1)
Call ReportDocBody.appendtext("(1) Owner field does not match 1st User name value (or Username(1) is not canonical): " & pers.fullname(0))
Call reportdocbody.addnewline(1)
sev(1) = True
End If

Having checked this, we then check that the name we use as the authentic canonical name, the owner field, has the same common name as that constructed from the first name and lastname. This matters, because a common name, and therefore a canonical name, that does not match the name on the ID file will also cause odd things to happen in name resolution. It was safe to do this check on firstname and lastname only for this customer because they don't use the middle initial, but if you do use middle initials, you should modify this code.

'2 check that the Id file name is firstname/lastname.
If Lcase(realfullname.common) <> Lcase(Trim(pers.firstname(0) & " " & pers.lastname(0))) Then
Call reportdocbody.addtab(1)
Call ReportDocBody.appendtext("(2) Notes ID file name does not match firstname/lastname 'human name': " & pers.firstname(0) & " " & pers.lastname(0))
Call reportdocbody.addnewline(1)
sev(2) = True
End If

This next piece of code checks that the common name that we have assumed will be on the ID file is present somewhere in the Fullname field. It's usually the second entry, but it doesn't have to be. Therefore we loop around all the entries and check each one. While we're at it, we also check whether the firstname/lastname combination is somewhere in Fullname. These (the ID file common name and the person record firstname/lastname) should actually be the same, but in case they aren't, we check that both exist.


1  ·  2  ·  3  ·  4  ·  5  ·  Next »
Other articles you might like
Home > Lotus Technologies > LotusScript (64 articles)
   When the debugger won't debug hidden code that isn't hidden
   What to do if the LotusScript debugger won't single-step over code
   Little known traps about Lotus Notes fields
Get Weekly Email Updates
Subscribe to our regular weekly email newsletter. It's packed with tips, reviews, deep analysis, and the latest news.
 
Recent DominoPower Articles
Lotusphere 2010: mobility and collaboration
2010: A Lotusphere of change
Five trends for 2010
DominoPower TV Episode 1: Inside a strategy session with Teamstudio
More about Domino log files
Say goodbye to the Uh-Ohs. Long live the Tens.
Why your log.nsf might not be purging properly
Latest Lotus Headlines
Recommended Maintenance - Lotus Notes Traveler
Here are the slides and other materials from our Lotusphere session
Microsoft OCS awareness in Lotus Connections and Websphere Portal?
SnTT: XPages Blank Calendar Control (Part 2), adding data
Have your Lotus Notes calendar display multiple time zones
Sample Database for Microsoft Office and Lotus Symphony Integration
Symphony 3.0 beta signals another attack on Office
>> Read all the news
More from the ZATZ journals
Computing Unplugged: The iPad: Apple's latest heartbreaker
David Gewirtz Online: CNN commentary and analysis
OutlookPower: Running auto-respond rules when Outlook is closed
-- Advertisement --

Learn Notes and Domino 8 at your place and pace!
Learn Notes and Domino in your office and/or home! TLCC's highly acclaimed distance learning courses for users, developers, and admins will enhance your career and your resume.

The many included activities and demos will make you a pro! Expert instructor help is a click away.

Click here to try a FREE demo course!!

-- Advertisement --

Mark your calendar for in-depth Lotus training, May 12-14, Boston
Join experts and peers May 12-14 in Boston for educational and networking events that deliver real-world Lotus training so you can increase productivity and efficiency in your company, advance your skills, and squeeze the most from your current environment. One registration gets you into THE VIEW's Admin2010 and Lotus Developer2010.

Register by December 31 to save $350.
ZATZ Home  ·  News  ·  Back Issues  ·  Credits/Trademarks ·  Link To Us
Copyright © 1998-2010, ZATZ Publishing. All rights reserved worldwide.
Editor's Login