<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from rtf -->
<style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<font face="Arial, sans-serif" size="3">
<div>Hi listers,</div>
<div>Ten years ago, when we moved over to an Oracle back end from CISAM, we made the decision to keep using zero for dates with no value.</div>
<div>This is fine if you only want to use Powerhouse to access the data, but anything else (including Oracle) complains loudly and at length about invalid dates.</div>
<div>Talking to Cognos, there&#8217;s a &#8220;DEFAULT DATE IS NULL&#8221; option on the database statement which <i>entirely transparently</i> translates NULL dates in the database into zero value dates for consumption by Powerhouse.</div>
<div>Does it work? Does it work transparently?</div>
<div>Does anyone have experience of using it? I guess if you&#8217;re using a SQL Server back end or an ODBC connection you have no choice.</div>
<div>More importantly, does anyone have any experience of turning this option on for a very mature database?</div>
<div>The upgrade path (make columns nullable, use QTP to set them to null, turn option on, recompile) would seem to be fairly simple, but are there any gotchas?</div>
<div>Many thanks in advance,</div>
<div>Stephen.</div>
<div>&nbsp;</div>
<div>&nbsp;</div>
<a name="_MailAutoSig"></a>
<div>--</div>
<div>Stephen Hulbert</div>
<div>Senior Analyst Programmer</div>
<div>For and on behalf of</div>
<div>Littlejohn LLP</div>
<div>Direct: 020 7516 2201</div>
<div>&nbsp;</div>
<div>&nbsp;</div>
</font>
<br><br><table bgcolor=white style="color:black"><tr><td><br><br>
<br>
Littlejohn<br>
1&nbsp;Westferry&nbsp;Circus<br>
Canary&nbsp;Wharf<br>
London<br>
E14&nbsp;4HD<br>
<br>
T:&nbsp;020&nbsp;7516&nbsp;2200<br>
F:&nbsp;020&nbsp;7516&nbsp;2400<br>
www.littlejohnllp.com<br>
<br>
Littlejohn&nbsp;LLP,&nbsp;Chartered&nbsp;Accountants<br>
<br>
The&nbsp;information&nbsp;contained&nbsp;in&nbsp;this&nbsp;communication&nbsp;is&nbsp;confidential&nbsp;and&nbsp;may&nbsp;be<br>
legally&nbsp;privileged.&nbsp;It&nbsp;is&nbsp;intended&nbsp;solely&nbsp;for&nbsp;the&nbsp;use&nbsp;of&nbsp;the&nbsp;individual&nbsp;or<br>
entity&nbsp;to&nbsp;whom&nbsp;it&nbsp;is&nbsp;addressed&nbsp;and&nbsp;others&nbsp;authorised&nbsp;to&nbsp;receive&nbsp;it.&nbsp;If&nbsp;you<br>
are&nbsp;not&nbsp;the&nbsp;intended&nbsp;recipient&nbsp;you&nbsp;are&nbsp;hereby&nbsp;notified&nbsp;that&nbsp;any&nbsp;disclosure,<br>
copying,&nbsp;distribution&nbsp;or&nbsp;taking&nbsp;of&nbsp;any&nbsp;action&nbsp;in&nbsp;reliance&nbsp;on&nbsp;the&nbsp;contents&nbsp;of<br>
this&nbsp;information&nbsp;is&nbsp;strictly&nbsp;prohibited&nbsp;and&nbsp;may&nbsp;be&nbsp;unlawful.<br>
&nbsp;<br>
Littlejohn&nbsp;LLP&nbsp;reserves&nbsp;the&nbsp;right&nbsp;to&nbsp;monitor&nbsp;the&nbsp;content&nbsp;of&nbsp;any<br>
message&nbsp;sent&nbsp;to&nbsp;or&nbsp;from&nbsp;littlejohnllp.com.<br>
<br>
Littlejohn&nbsp;LLP&nbsp;is&nbsp;registered&nbsp;as&nbsp;a&nbsp;limited&nbsp;liability&nbsp;partnership&nbsp;in&nbsp;England&nbsp;and&nbsp;Wales&nbsp;No.&nbsp;OC342572.&nbsp;&nbsp;<br>
Registered&nbsp;office&nbsp;as&nbsp;above.<br>
&nbsp;<br>
Any&nbsp;reference&nbsp;to&nbsp;a&nbsp;partner&nbsp;is&nbsp;to&nbsp;a&nbsp;member&nbsp;of&nbsp;the&nbsp;limited&nbsp;liability&nbsp;partnership.&nbsp;<br>
A&nbsp;list&nbsp;of&nbsp;members&nbsp;is&nbsp;available&nbsp;at&nbsp;the&nbsp;registered&nbsp;office.<br>
<br>
Littlejohn&nbsp;Advisors&nbsp;LLP&nbsp;is&nbsp;a&nbsp;limited&nbsp;liability&nbsp;partnership&nbsp;registered&nbsp;in&nbsp;<br>
England&nbsp;and&nbsp;Wales&nbsp;No.&nbsp;OC331599.&nbsp;Registered&nbsp;office&nbsp;as&nbsp;above.</td></tr></table></body>
</html>