- What are you hiding from me?
By now you should be able to extract your database design as DXL. This opens a series of possibilities to run reports against your database to gain more insights into its design. Since Notes is around for so many years you will face the situation to inherit a database you haven't written. To understand its logic you need so see how Hide-when formulas have been used in the all over design. The following XSLT allows you to do this extraction.
Use it at a starting point and play with the layout. Ideas you could look at: Pack the whole report into a single table and load it into your favorite spreadsheet for sorting (a fancy Ajax lib could do that to).
<xsl:stylesheetversion="1.0"
>
<xsl:outputmethod="xml"version="1.0"encoding="UTF-8"indent="yes"
/>
<xsl:templatematch="/"
>
<html
>
</xsl:template>
<head
>
<title
/>
<styletype="text/css"
/>
</head>
<body
>
</html>
<table
>
</body>
<xsl:apply-templatesselect="//d:form"
/>
<xsl:apply-templatesselect="//d:subform"
/>
</table>
<xsl:templatematch="d:form"
>
<tr
>
<thcolspan="3"
>
</tr>
<h1
>
Form
</th>
<xsl:value-ofselect="@name"
/>
</h1>
<tr
>
<th
/>
<th
/>
<th
/>
</tr>
<xsl:apply-templatesselect="//d:pardef[d:code/@event='hidewhen']"
/>
</xsl:template>
<xsl:templatematch="d:subform"
>
<tr
>
<thcolspan="3"
>
</tr>
<h1
>
Subform
</th>
<xsl:value-ofselect="@name"
/>
</h1>
<tr
>
<th
/>
<th
/>
<th
/>
</tr>
<xsl:apply-templatesselect="//d:pardef[d:code/@event='hidewhen']"
/>
</xsl:template>
<xsl:templatematch="d:pardef"
>
</xsl:stylesheet>
<tr
>
</xsl:template>
<tdbgcolor="#EEEEFF"
>
<xsl:value-ofselect="@id"
/>
</td>
<tdbgcolor="#EEFFEE"
>
<xsl:value-ofselect="d:code/@enabled"
/>
</td>
<tdbgcolor="#FFEEEE"
>
</tr>
<xsl:value-ofselect="d:code[@event='hidewhen']/d:formula"
/>
</td>
| Permalink | 
