FILE maximum reached!

[Pickering, John (NORBORD)]

One of the easiest ways I've found to free up file statements is to identify
those reference files which are in the screen just to validate a code and/or
get a description for it. It's a rare screen with 31 files that doesn't have
at least a couple of these.

I would then create a ghost screen to do the validation and pass back the
description. Call it from the input procedure of the field to be validated,
pass it the contents of fieldtext, a flag for ok or not ok and an item for
the description. The ghost screen does everything in the initialize
procedure. Do a get file optional using the value passed from the big
screen, test accessok and set the flag appropriately, set the temp to the
description or whatever and return. The big screen can then test the value
of the flag and issue the error message or carry on as normal. Yup, it's a
bit more coding than I'd like in a 4gl but it gets around the file limit.

Regards,
JWP

-----Original Message-----
From: Olmos, Fernando (Sericon at Alcoa)
[mailto:Fernando.Olmos@alcoa.com.au]
Sent: Sunday, February 23, 2003 10:15 PM
To: 'powerh-l@cube.swau.edu'
Subject: FILE maximum reached!


I am sure you guys have come across this before countless times. My problem
is, how do I compile a program that has reached its limit in  the number of
possible FILE statements?

I believe the max is 31 files per QUICK screen. What if you had to add
another to make it 32?

I know there is a simple solution, which I cannot remember what it was, but
I think it involved splitting the screen into two programs. Is there
examples of this?

Cheers