Jan-Erik Söderholm wrote on 08/27/2008
12:12:33 PM:

> Hi.
>
> Many years back I used JetForm for printed form
> processing on VMS (mVAX 3100/90 at the time).
> This works just OK. JetForm Design was used on
> a Windows PC to "design" the forms and then
> JetForm Merge was run on the VMS box to "merge"
> the application data with the forms and printed
> on standard lasers, usualy HP LaserJet 4's at the
> time.
>
> As far as I have found out, JetForm was bought
> by Adobe and VMS support was dropped some years ago.
>
> Now, is there anything available today similar
> to this tools ?
>
> Jan-Erik.

FlexForm Software

CONTACT
Contact Productive Systems, Inc using one of the forms at the left, or
directly to one of the offices listed here.
Home Office:
Productive Systems, Inc.
2610 Bond Street
Rochester Hills, MI 48309
Tel: 248.853.7500
Fax: 248.853.1460
European Support Office:
PSI Europe LTD.
c/o King & Taylor
10-12 Wrotham Road
Gravesend, Kent DA11 0PE
©Productive Systems, Inc all rights reserved
email info@flexform.com
2610 Bond Street
Rochester Hills, MI 48309
248.853.7500

[Disclaimer: I have no beneficial interest. I just use it.]

norm.raphael@metso.com wrote:
>
> Jan-Erik Söderholm wrote on 08/27/2008
> 12:12:33 PM:
>
> > Hi.
> >
> > Many years back I used JetForm for printed form
> > processing on VMS (mVAX 3100/90 at the time).
> > This works just OK. JetForm Design was used on
> > a Windows PC to "design" the forms and then
> > JetForm Merge was run on the VMS box to "merge"
> > the application data with the forms and printed
> > on standard lasers, usualy HP LaserJet 4's at the
> > time.
> >
> > As far as I have found out, JetForm was bought
> > by Adobe and VMS support was dropped some years ago.
> >
> > Now, is there anything available today similar
> > to this tools ?
> >
> > Jan-Erik.
>
> FlexForm Software
>
> *CONTACT*
>
> Contact Productive Systems, Inc using one of the forms at the left, or
> directly to one of the offices listed here.
>
> *Home Office:*
> Productive Systems, Inc.
> 2610 Bond Street
> Rochester Hills, MI 48309
> Tel: 248.853.7500
>
> Fax: 248.853.1460
>
> *European Support Office:*
> PSI Europe LTD.
> c/o King & Taylor
> 10-12 Wrotham Road
> Gravesend, Kent DA11 0PE
>
> ©Productive Systems, Inc all rights reserved
>
> email _info@flexform.com_
>
> 2610 Bond Street
> Rochester Hills, MI 48309
> 248.853.7500
>
> [Disclaimer: I have no beneficial interest. I just use it.]
>

OK, I've mailed them.
Their web site was a bit "thin", so I've asked for
further info. Are you able to describe a little
deaper how you're using this product(s) ?

Jan-Erik.

norm.raphael@metso.com wrote:

>
> Jan-Erik Söderholm wrote on 08/27/2008
> 12:12:33 PM:
>
> > Hi.
> >
> > Many years back I used JetForm for printed form
> > processing on VMS (mVAX 3100/90 at the time).
> > This works just OK. JetForm Design was used on
> > a Windows PC to "design" the forms and then
> > JetForm Merge was run on the VMS box to "merge"
> > the application data with the forms and printed
> > on standard lasers, usualy HP LaserJet 4's at the
> > time.
> >
> > As far as I have found out, JetForm was bought
> > by Adobe and VMS support was dropped some years ago.
> >
> > Now, is there anything available today similar
> > to this tools ?
> >
> > Jan-Erik.
>
> FlexForm Software
>
> [Disclaimer: I have no beneficial interest. I just use it.]
>

OK, I now have an demo/evaluation copy installed on
my VMS/Alpha. "Someone" told FLEXForm I was interested... :-)

Anyway, there are a few things. I will test it when
back in office on Monday, but thought I'd mention
it anyway.

FF (FLEXform) supports PCL5e as printer language.

DCPS claims to support PCL4, according to the current
docs. My thought was to route the FLEXform printouts
throught DCPS to be able to take advantage of the
Postscript printers we have. We'll see if DCPS will
complain on the FF output.

That's the major potential problem. I might report
back later, if anyone is interested.

I wounder if DCPS would be updated to support (at least)
PCL5e which have been the PCL standard version since
quite many years now ?

Jan-Erik.

In article , =?ISO-8859-1?Q?Jan-Erik_S=F6derholm?= writes:
>norm.raphael@metso.com wrote:
>
>>
>> Jan-Erik Söderholm wrote on 08/27/2008
>> 12:12:33 PM:
>>
>> > Hi.
>> >
>> > Many years back I used JetForm for printed form
>> > processing on VMS (mVAX 3100/90 at the time).
>> > This works just OK. JetForm Design was used on
>> > a Windows PC to "design" the forms and then
>> > JetForm Merge was run on the VMS box to "merge"
>> > the application data with the forms and printed
>> > on standard lasers, usualy HP LaserJet 4's at the
>> > time.
>> >
>> > As far as I have found out, JetForm was bought
>> > by Adobe and VMS support was dropped some years ago.
>> >
>> > Now, is there anything available today similar
>> > to this tools ?
>> >
>> > Jan-Erik.
>>
>> FlexForm Software
>>
>> [Disclaimer: I have no beneficial interest. I just use it.]
>>
>
>OK, I now have an demo/evaluation copy installed on
>my VMS/Alpha. "Someone" told FLEXForm I was interested... :-)
>
>Anyway, there are a few things. I will test it when
>back in office on Monday, but thought I'd mention
>it anyway.
>
>FF (FLEXform) supports PCL5e as printer language.
>
>DCPS claims to support PCL4, according to the current
>docs. My thought was to route the FLEXform printouts
>throught DCPS to be able to take advantage of the
>Postscript printers we have. We'll see if DCPS will
>complain on the FF output.
>
>That's the major potential problem. I might report
>back later, if anyone is interested.
>
>I wounder if DCPS would be updated to support (at least)
>PCL5e which have been the PCL standard version since
>quite many years now

If you have a postscript printer, you don't need anything beyond
DCPS. Define the form with postscript in a form dictionary and
then redefine the showpage command to execute execform with the
on the stack. I've been creating postscript forms for customers
this way for many years.


--
VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)COM

.... pejorative statements of opinion are entitled to constitutional protection
no matter how extreme, vituperous, or vigorously expressed they may be. (NJSC)

Copr. 2008 Brian Schenkenberger. Publication of _this_ usenet article outside
of usenet _must_ include its contents in its entirety including this copyright
notice, disclaimer and quotations.

In article ,
Jan-Erik Söderholm wrote:

> I wounder if DCPS would be updated to support (at least) PCL5e which
> have been the PCL standard version since quite many years now ?

Updating the DCPS PCL translator from PCL 4 to a newer PCL version is
not on our list of enhancements. We believe there is such little need
for it that it would not be worth the effort.

These days, most PostScript printers have PCL interpreters and DCPS will
happily pass PCL files over to the printer. In Days of Yore, when many
printers had PostScript and ANSI, but no PCL, the DCPS PCL translator
provided a useful function, printing PCL files on a printer that
otherwise could not print them.

If someone has a need for an upgraded DCPS PCL translator, let me know.

Paul

--
Paul Anderson
OpenVMS Engineering
Hewlett-Packard Company

Paul Anderson wrote:
> In article ,
> Jan-Erik Söderholm wrote:
>
>> I wounder if DCPS would be updated to support (at least) PCL5e which
>> have been the PCL standard version since quite many years now ?
>
> Updating the DCPS PCL translator from PCL 4 to a newer PCL version is
> not on our list of enhancements. We believe there is such little need
> for it that it would not be worth the effort.
>
> These days, most PostScript printers have PCL interpreters and DCPS will
> happily pass PCL files over to the printer.

OK, no matter what level of PCL ?
DCPS just doesn't care, I guess...

> If someone has a need for an upgraded DCPS PCL translator, let me know.

No, I can't say I/we "need" this right now (or ever).

Thanks for replying anyway.

Jan-Erik.


>
> Paul
>

In article ,
Jan-Erik Söderholm wrote:

> OK, no matter what level of PCL ? DCPS just doesn't care, I guess...

DCPS doesn't know or care what version of PCL will be interpreted by the
printer.

Paul

--
Paul Anderson
OpenVMS Engineering
Hewlett-Packard Company