note sundialsvc4 <p> To me, consistency is key. &nbsp; If your application has to work alongside other code (e.g. in VB) that already uses this nomenclature, then follow suit. &nbsp; If you are working with a legacy application that didn&rsquo;t use it, don&rsquo;t introduce it. &nbsp; Figure out what the Romans were doing and keep doing it. </p><p> These notations can unintentionally be <em>misleading</em> when used with a &ldquo;typeless&rdquo; language, such as Perl is and such that VB often is. &nbsp; You can legitimately find that your <tt>szFoo</tt> variable contains an integer, or that the value it contains has magically transmogrified itself into one. &nbsp; Thus, the social-contract that has been <em>implied</em> by the naming can&rsquo;t be upheld by the technology, which might produce confusion.&nbsp; Nevertheless, human beings will still benefit from consistency in naming, whatever that consistency is. </p> 1014477 1014477