Don't fret if you couldn't pass this test. You'll be able to after you read this article and implement the agent it describes. And you won't have to spend extra money on a product that analyzes the databases on your system. All you need is a single LotusScript agent, a form to capture the information and a few views to help you analyze at a glance what you have on your system.

You won't even need to worry about searching through all of your subfolders. The agent will provide a report on all databases off of your main Notes data directory, regardless of whether or not they are in subfolders.

Time to do a little housecleaning?
We've all reached a point when we've had to delete some files off of our computer to save space. We even sometimes have to delete (GASP!) Notes/Domino databases. During a recent spring-cleaning frenzy, I went into Windows Explorer, opened up the C:\NOTES\DATA folder and then chose to view the files by size. This is fine when you're starting on a new computer and you only have a few databases on your local machine, which you can identify by the file names. Now that I've been at my current job for over six months, however, I've got a lot of Notes database files on my local machine and I can no longer identify them by file name alone.

You could browse through the databases by selecting them on the Workspace tab, opening them up by looking at all of the elements, and then deciding if you want to delete them or not. Then you could choose Database->Delete from the File menu to actually delete the database from your hard drive. But if you're like me, you have 14 Workspace tabs and it's a pain to have to go through all of the databases one-by-one and decide what to keep and what to delete. It would be much easier to look at all of your databases in a single view and then immediately drill down to more detailed information about selected databases.

What I needed was something to analyze what databases I had on my computer. Then that something would tell me all the pertinent information I needed to know about those databases to help me decide which ones I should keep and which I should scrap. I also wanted something that would help me when doing development. This tool would list the names of all of the forms and views in a database along with their aliases. Since I always develop with an eye to Web functionality, I use aliases on all of my forms and views so I won't have to insert "+" signs to replace spaces in a name when putting it into a URL.