Re:SFL Print Screen

["Michael Naughton" <mnaughton@xxxxxxxxxxxx>]

Hi Luis,

I think said it very succintly - print screen will show you the screen
only (after all, how can it possibly know what's going on in your program?

However, I don't think that setting up a separate report should be that
big a deal. I'd recommend using a print file with two record formats: one
for your subfile header and one for the detail line. Use the same field
names as you use in the display file. Then in your program you can simply
WRITE the header format and then loop through your subfile WRITEing all
the records.

I admit I've never been much of a print file fan (maybe it had something
to do with RLU ;-), but I had to do something similar to this recently and
it worked out great. I was impressed at how easy it was, and for the first
time I saw what a handy tool the print file can be.

PS: And now for a question of my own (maybe this should move to the
CODE400 list?): is there an easy way -- maybe using CODE -- to convert a
display file into a print file? In my project, I ended up using SEU to go
in and clean up the source file -- not really difficult, but kinda boring
and tedious. I know CODE makes working with print files much easier -- is
there an easy way to do this kind of conversion?

>Luis, The PRINT key only it prints the contents of the *screen*, nothing
>more, nothing less. If you want to extend this functionality, then you
>must write the necessary logic. And, as Peter suggested, I would not use
>the PRINT key for this - I would use another function key, since your
>users are probably already accustomed to using the PRINT key as
>originally designed. You do want consistency throughout your
>applications, right? Steve 


Mike Naughton
Senior Programmer/Analyst
Judd Wire, Inc.
124 Turnpike Road
Turners Falls, MA  01376
413-863-4357 x444
mnaughton@xxxxxxxxxxxx