There are different reasons why you might need to archive old Lotus Notes databases, and an almost infinite number of different approaches to the archive process. In this article, we take a look at the different ways this can be done, along with an analysis of the pros and cons of each approach.

The original versions of the fairytales written by the Brothers Grimm were far, far scarier and more bloodthirsty than later versions. They were modified over time to become more child friendly. These days, once a book is written, it rarely gets updated to v2.0 with a new, improved plot. Software, on the other hand, does get regularly updated, and it’s a good idea to have some tools to help manage that process.

The Lotus Notes client - love it or hate it, you have to have it, if you want to run traditional Lotus Notes/Domino applications. But soon, with the release of HCL Domino v12 will come Nomad Web, and with it the ability to finally retire your Lotus Notes clients. It’s like magic!

Much has been written about software quality over the years. But most of the literature refers to tools and techniques that are used in mainstream development environments. What about traditional HCL Domino apps, built using Domino Designer? Isn’t it just as important to worry about software quality for these apps too?

For probably 98% of cases, an HTML archive of a Notes database created with Teamstudio Export will show you exactly the information you need to see. But sometimes, there are those tricky cases where you need to be able to tweak the interface just a little bit to be able to unhide a hidden view, or show a field that wouldn’t appear in the Notes UI. If that sounds familiar, here’s how to tailor the HTML output so that it fits exactly what you need.