Posted by smoore on Fri, 5 Sep 2003 11:05:10 :
05 September 2003
Hello Support:
Moore Greens Inc. =95 From the desk of Steven Moore
We are running Comet 2000 build 293.
-----------------------------------------------------
We use escape codes in some of our IB programs. Most of the time it is =
to turn on/off bold, expanded, or italicized print. These are for HP =
DeskJet's and LaserJet's.
As these codes are hard written in the print formats, when choosing to =
print to LPT, or any non-HP printer, the escape sequence gets displayed =
both before and after our titles.
Is there a way to suppress escape codes from printing on paper or =
terminal printers as '1B2e55' etc. or is it left to programming to test =
for printer type, and use format HP for HP printers, and format NHP for =
non-HP printers?
-----------------------------------------------------
We have declared in the ini file a terminal printer LPT. I have been =
using QREPORT to run programs with output to PRINTER LPT. When I do =
this, I get 3-boxes at the end of some lines. Also, when running an IB =
program, any instance of (LF) gets displayed as 3-boxes. =20
While I have a workaround for the IB issue, I replace (LF), with =
(CR);'@20@';(CR) and all is fine. I cannot fix the QREPORT issue. Is =
this due to my choices? Is there a fix with newer releases?
------------------------------------------------------
This problem has been long lived. I only noticed it recently though.
I have an IB program that is a compound equation. XX =3D XQTY * =
((1.0000*XUNITPC)/XQUNIT) where it is similar to xunitpc =3D 12 and =
xqunit =3D 245 and xx is declared 9.2 which in reading on website, seems =
to be the problem.
In the old Qantel days, including 1.0000 expanded the natural length of =
calculation. IB does not do that. The resultant controls the length. =
Is this corrected in newer version of Comet? =20
I thought of a workaround as declaring a new system variable VARCLC as =
18.9, and ROUND, and letting VARCLC =3D (original compound equation) =
then next line letting (original resultant) =3D VARCLC. I have tested =
this out and now resultants are accurate. Any time an equation went =
beyond X.2 to the right, it was blown away. Lucky for us, it was never =
an issue on commission and cost reports. But it did have a major impact =
on our manufacturing modules!
---------------------------------------------------