× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Guess I was making it too hard. Added the second record and it is so
slick. THANKS!

John McKee

Quoting "Scott, Bill" <Bill.Scott@xxxxxxx>:

Simply put the BOX command on a different record, then you do not
have to change everything to POSITION. I usually use "normal" spacing
for the detail lines of the invoice/packing list, whatever and just
use POSITION when you absolutely have to have perfect placement.


Bill Scott
Océ North America, Inc.
Tel.: (561) 997-3256
e-mail: Bill.Scott@xxxxxxx

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of John McKee
Sent: Tuesday, February 10, 2009 1:28
To: Midrange Systems Technical Discussion
Subject: Printer file positioning

Just completed work on the first printer file I have built from
scratch in over twenty years.

I saw a nice keyword, BOX. I wanted to use this to surround a
portion of the report. But, using that keyword requires that
POSITION be used on all other entries.

What I don't understand is that, from what I have read, that the
values used for POSITION are related to the UOM at the time the
printer file is created.
Problem is I was attempting to convert row/column to position values.
PDM complains when it sees POSITION(10 60). So, obviously, PDM is
not looking at the row column UOM, but is defaulting to inches.

The way I read the manual, it is possible to specify row and column.
Is that correct? If so, how do I get PDM to not complain? I don't
see anything in the options that effects how the syntax checker
interprets values supplied to the POSITION keyword.

John McKee

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
http://archive.midrange.com/midrange-l.



This message and attachment(s) are intended solely for use by the
addressee and may contain information that is privileged,
confidential or otherwise exempt from disclosure under applicable law.

If you are not the intended recipient or agent thereof responsible
for delivering this message to the intended recipient, you are hereby
notified that any dissemination, distribution or copying of this
communication is strictly prohibited.

If you have received this communication in error, please notify the
sender immediately by telephone and with a 'reply' message.

Thank you for your co-operation.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.






As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.