FP Support answers

[Ken Cole]

Richard,

Are you aware there is an online manual that will answer a lot of questions?

For your second question:

Syntax:

       Then: close
       Then: close filename

Use CLOSE by itself to close all files except the current file.

Use CLOSE filename to close an individual file, where "filename" is a
lookup file name, or an export file name. CLOSE can be used on all
processing tables.


As for your first question, I think the suggestion to use the system array
to see what files are open was a good suggestion as it will either confirm
or deny your suspicions that "all of the screens" get opened. I don't think
that is correct.  From what you have stated we must assume, and that is
never a good thing, that you are using [dr]clerk and input processing since
your mentioned screens.  I believe filePro will open auto, input, key,
data, all indexes and the current screen of the input table and then key,
data and the index being used for each lookup.  That may be all indexes but
hey the file array would tell us 100% without guessing!


You are correct about there being an "auto close" feature at some time.


If you had read the online manual for System Arrays you would have found
this


@ALLFILES[]

Contains a list of all files open by filePro, even those closed due to
dynamic open/close. Some entries may be blank, representing an unused (i.e.
closed) file.


I hope that helps, don't forget the old programmers adage RT[F]M :-)


Regards


Ken

On Thu, 20 May 2021 at 02:27, Richard Kreiss via Filepro-list <
filepro-list at lists.celestial.com> wrote:

> To all,
>
> I appreciate that FP support responds in a very timely manner.
>
> But, I take issue with their responses sometimes.  If one asks a specific
> question and it is not answered, although they may think the response
> covers it, the questioner may not find the response answering their
> question.
>
> I received an error message during an output to too many files were open
> and filePro could only handle 60 files.  I asked if this could be increased
> and could I add a close to the lookups?  I recalled a long time ago that a
> lookup opened the key and data files as well as all of the screens and
> indexes.  At some point an auto close was added that closed the lookup
> without having to put an explicit close lookup alias file name in the
> processing. I am wondering if something has changed since that time back in
> the 1990's?
>
> My second question was will a close lookup name work.
>
> Supports comment was to add the system array allfiles the  only problem is
> that I would have to add this after each lookup in the processing table to
> see what is open at each point before the error message comes up.   Thisa
> does not directly answer my question "will a close lookup name work.  It
> may be easier to add a close to each lookup then figure out when to add
> popup showing all the files that are open. I can guess which lookup cause
> the most files to be opened and close those files which have the most
> screens and indexes associated with them.  I must keep in mind that auto
> processing does lookups also and those need to be closed also.
>
>
> Richard Kreiss
> GCC Consulting
>
>
>
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: winmail.dat
> Type: application/ms-tnef
> Size: 15595 bytes
> Desc: not available
> URL: <
> http://mailman.celestial.com/pipermail/filepro-list/attachments/20210519/0fb42587/attachment.bin
> >
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> Subscribe/Unsubscribe/Subscription Changes
> http://mailman.celestial.com/mailman/listinfo/filepro-list
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.celestial.com/pipermail/filepro-list/attachments/20210520/2eefed17/attachment.html>