Wow, Didn't See this Coming

Over the past couple of days I have been trying to trace a bug in my code without any resolution, until today. Wasted days of precious time. I trace down the issue and discovered it was the result of another odd behavior of Lotus Notes. I do not know if this applies to other versions of Lotus Notes, but I can guess it does. In the Lotuscript database class, NotesDatabase, the property Notesdatabase.Server is used often. It should return the server name in the following format:

CN=Acme01/O=Acme

This is fine, but if you get the same property in a dialog box, you WILL NOT get the same format. Instead the format is:

Acme01/Acme

So when I was parsing the server name I would get different results causing a chain of errors that resulted in hours of time tracing the error in code that has been working for years. What a pain. As we push Notes and Domino more and more into a new level, we are finding more and more things to watch out for.

Comments

Theo Heselmans (Xceed) said…
Very strange, never had a problem with this. But a tip: don't parse, use NotesName:

Dim servername As NotesName
Dim currentserver As String

Set servername=New NotesName(db.server)
currentserver=servername.Common

Hope this helps.
November 21, 2008 at 1:43 AM
Anonymous said…
"parsing"...

Seems like you handle the server name like a string. Why not create a Notesname instead and handle the server name in proper way?

Brgds Jesper Kiaer

http://www.nevermind.dk
November 21, 2008 at 6:39 AM
Anonymous said…
"parsing"...

Seems like you handle the server name like a string. Why not create a Notesname instead and handle the server name in proper way?

Brgds Jesper Kiaer

http://www.nevermind.dk
November 21, 2008 at 6:44 AM
Domino Interface said…
Theo and Jesper,

Thanks. For some reason that never cross my mind. That works.
November 21, 2008 at 6:48 AM
Post a Comment

Popular posts from this blog

The iPhora Journey - Part I - Reimagining Domino

Domino, which is currently owned by HCL Technologies, is one of the most enduring application platforms ever built. It owes its existence to Ray Ozzie, who was heavily influenced by his use of the PLATO system, a pioneering interactive/educational network at the University of Illinois. The first version of Domino (then called Lotus Notes) was released in 1989, and Domino applications from 1989 can still run on the newest version (12.01). You can build Domino applications for deployment on the Notes clients, mobile devices, or Web browsers, and for programming and customization, you can use Nodejs, Java, LotusScript, and Formula language, or any combination of them. Regardless of which programming languages are used, a typical application is usually represented by a single Domino database. However, the IT landscape has changed significantly since Domino was a dominant player in the market. The migration to web and mobile applications using cloud-based solutions has led to the steep decl
Read more

Creating Composite Applications for Classic Lotus Notes Clients – Part 2

Image
This is part 2 of my creating composite application for classic Lotus Notes clients. In part 2, I will cover how a new event in Lotus Notes 8 can used to simplify the process of creating a composite application. You can download the demo code from the sidebar or download it from here. This new event is "onSelect" and is found in Notes View. This event works not only for regular views but also for embedded views and even embedded views within a dialog box. This event is triggered whenever a document is selected in a view. It hold true even when the view is display for the first time. As a Notes developer, I feel this one single event is more than enough reason to upgrade to at least the Lotus Notes 8 Basic client. It makes a number of UI issues simply go away. Just like in the previous Lotus Notes clients we need to create a launch document in our composite application that will be used to trigger the population of the frames in the composite application. However, rather than
Read more

The iPhora Journey - Part 5 - Dammit Jim, I'm a LotusScripter not a JavaScripter

Image
As often said by Dr. McCoy in the original Star Trek series, he is a doctor, not a ____________ .  However, just like Dr. McCoy, you may sometimes need to work on things that seem very alien to your experience.  One of those things, might be JSON. LotusScript, which was derived from Visual Basic, was written long before JSON existed, and therefore, LotusScript had no built-in capabilities for handling JSON objects. As we mentioned in Part 4, JSON plays a critical role in iPhora.  All data are stored as JSON, and JSON serves as the primary data and communication format between modules, functions and services.  All core components operate using JSON-based configurations.  Therefore, it was extremely important that we are able to fluidity create, read and process JSON.   Creating a JSON string is relatively easy in any programming language. You can create it even using Commodore 64 Basic, and if built sequentially, one line at a time, it is possible to create JSON representations of ve
Read more