<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
        {font-family:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
        {font-family:Consolas;
        panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
        {font-family:Garamond;
        panose-1:2 2 4 4 3 3 1 1 8 3;}
@font-face
        {font-family:"Arial Rounded MT Bold";}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
pre
        {mso-style-priority:99;
        mso-style-link:"HTML Preformatted Char";
        margin:0in;
        margin-bottom:.0001pt;
        font-size:10.0pt;
        font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
        {mso-style-priority:99;
        mso-style-link:"Balloon Text Char";
        margin:0in;
        margin-bottom:.0001pt;
        font-size:8.0pt;
        font-family:"Tahoma","sans-serif";}
span.HTMLPreformattedChar
        {mso-style-name:"HTML Preformatted Char";
        mso-style-priority:99;
        mso-style-link:"HTML Preformatted";
        font-family:Consolas;}
span.BalloonTextChar
        {mso-style-name:"Balloon Text Char";
        mso-style-priority:99;
        mso-style-link:"Balloon Text";
        font-family:"Tahoma","sans-serif";}
span.EmailStyle21
        {mso-style-type:personal;
        font-family:"Calibri","sans-serif";
        color:windowtext;}
span.EmailStyle22
        {mso-style-type:personal;
        font-family:"Garamond","serif";
        color:blue;
        font-weight:normal;
        font-style:normal;}
span.EmailStyle23
        {mso-style-type:personal;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
span.EmailStyle24
        {mso-style-type:personal;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
span.EmailStyle25
        {mso-style-type:personal-reply;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-size:10.0pt;}
@page WordSection1
        {size:8.5in 11.0in;
        margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
        {page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='color:#1F497D'>Character data is always truncated with no warning. If you had an indexed file item that was 10 characters and moved a 20 character value into it, the last 10 characters would be truncated with no warning. The difference with relational is that PowerHouse writes individual columns for efficiency.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>As for the dictionary elements, they are simply the logical view of the item adding validation and formatting options if specified. The length of the element is only a logical length and is only used as the default for non-relational files.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Bob<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><div><p class=MsoNormal><span style='color:#1F497D'>Bob Deskin<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>PowerHouse Consultant<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>UNICOM Global<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><a href="mailto:bob.deskin@unicomglobal.com">bob.deskin@unicomglobal.com</a><o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>(973) 526-3856<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>This message (including any attachments) contains confidential information that is PRIVILEGED, CONFIDENTIAL and/or ATTORNEY WORK PRODUCT and is intended only for the individual(s) named herein. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this email is strictly prohibited. If you have received this message in error, please notify the UNICOM Systems, Inc. Postmaster (<a href="mailto:postmaster@unicomsi.com">postmaster@unicomsi.com</a>) of the error immediately, do not read or use the email and any attachments in any manner, destroy all copies, and delete it from your system if the communication was sent via email. UNICOM Systems, Inc. (818) 838-0606 Fax: (818) 838-0776<o:p></o:p></span></p></div><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Thomson, Martyn [mailto:Martyn.Thomson@hpadvancedsolutions.com] <br><b>Sent:</b> Wednesday, April 08, 2015 5:02 PM<br><b>To:</b> Bob Deskin; Lorry Litman; powerh-l@lists.sowder.com<br><b>Subject:</b> RE: Why no record size mismatch error?<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span lang=EN-CA style='color:#1F497D'>I see. So data written from the buffer to the table will be truncated losing the last character, with no warning.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-CA style='color:#1F497D'>To answer Lorri’s question: yes, the fields were also increased in length in the PH Dictionary.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA style='color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Bob Deskin [<a href="mailto:bob.deskin@unicomglobal.com">mailto:bob.deskin@unicomglobal.com</a>] <br><b>Sent:</b> April-08-15 1:37 PM<br><b>To:</b> Lorry Litman; Thomson, Martyn; <a href="mailto:powerh-l@lists.sowder.com">powerh-l@lists.sowder.com</a><br><b>Subject:</b> RE: Why no record size mismatch error?<o:p></o:p></span></p></div></div><p class=MsoNormal><span lang=EN-CA><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>PowerHouse gets its schema information from the database. If you change a column, and it’s still consistent with what PowerHouse had, then there’s no error. PowerHouse writes and updates by column, not by row/record as for indexed files. Just because the column buffer is now shorter than the column in the database doesn’t cause an error for a character field.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Bob<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><div><p class=MsoNormal><span style='color:#1F497D'>Bob Deskin<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>PowerHouse Consultant<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>UNICOM Global<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><a href="mailto:bob.deskin@unicomglobal.com">bob.deskin@unicomglobal.com</a><o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>(973) 526-3856<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>This message (including any attachments) contains confidential information that is PRIVILEGED, CONFIDENTIAL and/or ATTORNEY WORK PRODUCT and is intended only for the individual(s) named herein. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this email is strictly prohibited. If you have received this message in error, please notify the UNICOM Systems, Inc. Postmaster (<a href="mailto:postmaster@unicomsi.com">postmaster@unicomsi.com</a>) of the error immediately, do not read or use the email and any attachments in any manner, destroy all copies, and delete it from your system if the communication was sent via email. UNICOM Systems, Inc. (818) 838-0606 Fax: (818) 838-0776<o:p></o:p></span></p></div><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> <a href="mailto:powerh-l-bounces+bob.deskin=unicomglobal.com@lists.sowder.com">powerh-l-bounces+bob.deskin=unicomglobal.com@lists.sowder.com</a> [<a href="mailto:powerh-l-bounces+bob.deskin=unicomglobal.com@lists.sowder.com">mailto:powerh-l-bounces+bob.deskin=unicomglobal.com@lists.sowder.com</a>] <b>On Behalf Of </b>Lorry Litman<br><b>Sent:</b> Wednesday, April 08, 2015 4:26 PM<br><b>To:</b> 'Thomson, Martyn'; <a href="mailto:powerh-l@lists.sowder.com">powerh-l@lists.sowder.com</a><br><b>Subject:</b> RE: Why no record size mismatch error?<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span lang=EN-CA style='font-size:12.0pt;font-family:"Garamond","serif";color:blue'>Hi Martin,<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA style='font-size:12.0pt;font-family:"Garamond","serif";color:blue'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-CA style='font-size:12.0pt;font-family:"Garamond","serif";color:blue'>I gather the domain was changed in RDB, but, were the two fields affected changed in the PH dictionary?<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA style='font-size:12.0pt;font-family:"Garamond","serif";color:blue'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-CA style='font-size:12.0pt;font-family:"Garamond","serif";color:blue'>When the QTP program updates the RDB table, do all 10 characters get updated or perhaps just 9 of 10?<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA style='font-size:12.0pt;font-family:"Garamond","serif";color:blue'><o:p> </o:p></span></p><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Garamond","serif";color:blue'>Thanx</span><span style='font-size:12.0pt;color:blue'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Garamond","serif";color:blue'>Lorry Litman</span><span style='font-size:12.0pt;color:blue'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Garamond","serif";color:blue'>Application Management</span><span style='font-size:12.0pt;color:blue'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Garamond","serif";color:blue'><a href="mailto:llitman@manitoba-ehealth.ca">llitman@manitoba-ehealth.ca</a></span><span style='font-size:12.0pt;color:blue'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Garamond","serif";color:blue'>204-926-9076</span><span lang=EN-CA style='color:blue'><o:p></o:p></span></p></div><p class=MsoNormal><span lang=EN-CA style='font-size:12.0pt;font-family:"Garamond","serif";color:blue'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> <a href="mailto:powerh-l-bounces+llitman=manitoba-ehealth.ca@lists.sowder.com">powerh-l-bounces+llitman=manitoba-ehealth.ca@lists.sowder.com</a> [<a href="mailto:powerh-l-bounces+llitman=manitoba-ehealth.ca@lists.sowder.com">mailto:powerh-l-bounces+llitman=manitoba-ehealth.ca@lists.sowder.com</a>] <b>On Behalf Of </b>Thomson, Martyn<br><b>Sent:</b> Wednesday, April 08, 2015 3:17 PM<br><b>To:</b> <a href="mailto:powerh-l@lists.sowder.com">powerh-l@lists.sowder.com</a><br><b>Subject:</b> Why no record size mismatch error?<o:p></o:p></span></p></div></div><p class=MsoNormal><span lang=EN-CA><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-CA>I increased the size of a domain from 9 to 10 chars. 2 fields use the domain and appear in 440+ tables.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-CA>Why does a QTP procedure not recompiled in years still work? It’s accessing one of said tables and a view of another. Surely it should generate a runtime error?<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-CA>OpenVMS 8.3<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA>Powerhouse 8.40G<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA>Oracle Rdb V7.2-501<o:p></o:p></span></p><p class=MsoNormal style='margin-top:6.0pt'><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'>Regards, <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA style='font-family:"Arial Rounded MT Bold";color:#1F497D'>Martyn Thomson<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA style='font-family:"Arial","sans-serif";color:#1F497D'>Senior Technical Analyst, Development Services</span><span lang=EN-CA style='font-family:"Arial Rounded MT Bold";color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA style='font-family:"Arial","sans-serif";color:#1F497D'>Information Technology Services<o:p></o:p></span></p><p class=MsoNormal><b><i><span style='font-size:14.0pt;color:#003D83'>HP Advanced Solutions Inc.<o:p></o:p></span></i></b></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'>phone: 250.405.4555 | fax: 250.405.4422</span><span lang=EN-CA style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'>email:<a href="mailto:martyn.thomson@hpadvancedsolutions.com">martyn.thomson@hpadvancedsolutions.com</a> </span><span lang=EN-CA style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'>web: <a href="http://www.hpadvancedsolutions.com/">www.hpadvancedsolutions.com</a> <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA><o:p> </o:p></span></p><pre><span lang=EN-CA>This e-mail message has been scanned and cleared by Postini / Google Message Security and the UNICOM Global security systems. This message is for the named person's use only. If you receive this message in error, please delete it and notify the sender. <o:p></o:p></span></pre><pre><span lang=EN-CA><o:p> </o:p></span></pre></div></body></html>
<pre>This e-mail message has been scanned and cleared by Postini / Google Message Security and the UNICOM Global security systems. This message is for the named person's use only. If you receive this message in error, please delete it and notify the sender.