Be sure you look at Booth's example...

If you want a window to work for a 24x80 and a 27x132 screen you have to
code it right.


On Wed, Aug 9, 2017 at 11:11 AM, Dan <dan27649@xxxxxxxxx> wrote:

On Wed, Aug 9, 2017 at 12:24 PM, Buck Calabro <kc2hiz@xxxxxxxxx> wrote:

given subfile.) I burned a lot of time just getting this to work, and
project is due in a few days.

It seems to me that for the most part, the only way we ever manage to
learn a better way is to spend that sort of time on an actual project.

Believe me, I get that. I am an independent contractor and am only allowed
to bill 40 hours per week. I will probably put in closer to 60 hours this
week to get this service program tweaked just right so that we have a solid
base to use going forward.

In this particular case, I'm not sure moving the WORKSTN file to each
procedure buys me anything. The display file has all of the prompt windows
defined in it, so it seems a natural fit to leave the WORKSTN spec at the
module level. Opening and closing the file in each procedure that uses it
is no big deal.

- Dan
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,
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives

Please contact support@xxxxxxxxxxxx for any subscription related

Help support by shopping at with our affiliate

This thread ...


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

This mailing list archive is Copyright 1997-2019 by 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].