|
And you're sure the overlay was created? No errors? And the cpyfrmpcd worked
correctly? Sounds like you're dealing with the old version of the overlay.
Check the create date with a dspobjd.
On Fri, Aug 21, 2009 at 2:50 PM, Jack Tucky <jacktucky@xxxxxxxxx> wrote:
Sorry. The original sets of signatures continue to work. Two new ones--
won't work.
No program changes or anything.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Michael Ryan
Sent: Friday, August 21, 2009 2:19 PM
To: Midrange Systems Technical Discussion
Subject: Re: Overlay not showing sometimes
It doesn't print sometime or never since you made the change? Does the old
copy still work?
On Fri, Aug 21, 2009 at 2:02 PM, Jack Tucky <jacktucky@xxxxxxxxx> wrote:
> We put an electronic signature on some Bills of Lading. The entire
printer
> file has an overlay, plus we put the signature in a little box at the
> bottom.
>
>
>
> This has been working well for several years. We needed to create some
new
> signatures, so I followed the steps I always do. Create the jpg, print
to
> the AFP 300 printer driver (specify medium overlay), put the file in
QDLS,
> then do the Create OVL
>
>
>
> Like this:
>
>
>
> CPYFRMPCD FROMFLR(&FLR) TOFILE(QTEMP/WORKF) +
>
> FROMDOC(&FILE) +
>
> TRNTBL(*NONE) TRNFMT(*NOTEXT)
>
>
>
> CRTOVL OVL(&LIB/&OVL) FILE(QTEMP/WORKF) MBR(WORKF)
>
>
>
>
>
> The overlay prints on a test form. BUT I can't get it to print in our
> application.
>
>
>
> Here is the DDS
>
>
>
> A R SIGN OVERLAY(&LIB/&OVLS &POSD &POSA)
>
> A LIB 10A P
>
> A OVLS 8A P
>
> A POSD 5S 3P
>
> A POSA 5S 3P
>
>
>
> I've confirmed via debug all of these field values are correct. I > don't
> mess with overlays much. Has anyone seen anything like this before?
>
>
>
> Jack
>
>
>
>
>
> --
> 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 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 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 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 mailing list archive is Copyright 1997-2025 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.