Re: Question for Printer Gurus

I agree that it would be better - as would many, many other options. But I'm stuck with printer files and nothing else.

I was hoping that more people here had had experience in globalizing their applications and had some thoughts on how best to handle printer files.


On 2014-09-03, at 3:23 PM, Alan Campin <alan0307d@xxxxxxxxx> wrote:

The best thing to do is use a GUI tool to develop reports but you may or
may not have access to that. SQL Reporting Services is great and free if
the company has SQL Server.


On Wed, Sep 3, 2014 at 1:16 PM, Booth Martin <booth@xxxxxxxxxxxx> wrote:

Facing the same sort of decision a few years ago I I chose to abandon most
*PRTF development and write all new reports and replace as many printed
reports as possible with formatted output. My favorite in that particular
environment turned out to be HTML with the reports published to a location
in the IFS, Users could order the report, review it on line, or print the
report with browser printing. Even simple, easily written HTML files,
with standard /copy headers and footers, combined with a simple .css file
were more attractive and printed more flexibly than using *PRTF files.
Plus, the users in many instances found the browser version more convenient
than the paper print outs.

Here are the beginnings of what I did as illustration of the process As
you will note, very primitive. Nut it works.
http://martinvt.com/Ice_Cream_Project/Ice_Cream__How-to/ice_
cream__how-to.html http://tinyurl.com/nxb5u4y

On 9/3/2014 8:09 AM, Jon Paris wrote:

I was rather afraid of that Birgitta, the only other option then seems to
be to take the approach that Booth did and load the fields in the logic,
but that's not a good solution either.

I can't believe that printer support is so poor compared with displays -
particularly since green screen are dying - but printer could go on forever.

Sigh ....



On 2014-09-03, at 1:02 AM, Birgitta Hauser <Hauser@xxxxxxxxxxxxxxx>
wrote:

Hi Jon,

We compiled multiple printer files, one for each language within the
"language" library using the appropriate message file.
At runtime we override the printer file before opening it.

Mit freundlichen Grüßen / Best regards

Birgitta Hauser

"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training
them
and keeping them!"


-----Ursprüngliche Nachricht-----
Von: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] Im Auftrag von
Jon
Paris
Gesendet: Wednesday, 03.9 2014 01:34
An: Midrange-L Midrange-l
Betreff: Question for Printer Gurus

I'm beginning to believe that the folks who did DDS for printer files
never
talked to the folks who did display files ...

Latest barrier in my conversion effort is lack of support for the MSGID
keyword on printer files. MSGCON is supported but that is of no use to me
since I need to be able to use the LIBL to control the message file that
is
used and MSGCON values are resolved at compile time as far as I can tell.

I know a number of you out there write apps that support multiple
languages
- how the heck do you handle that for printer files?


Jon Paris

www.partner400.com
www.SystemiDeveloper.com




--
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.

Jon Paris

www.partner400.com
www.SystemiDeveloper.com

--
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.

Jon Paris

www.partner400.com
www.SystemiDeveloper.com