FP Support answers

[Richard Kreiss]

I am aware of the online manual. However I have found that some things are not listed there or missing. 

I had to put @allfiles in a number of places and found that one of the files opened is the r* file created by filePro in the temp folder being used. Also it is difficult to show all of the files as each file is in an element of the array. A= @all-files(“1”);msgbox a or used show statements to display the array elements. I could get the last file name by looking for an empty array element and then showing the array element before the empty one. 

Keep in mind that I was testing a client program in his system and received this error, this was the third day of testing. I had not gotten this error message previously and needed to know why and where to look quickly. I did not have time to search the on-line manual for an answer. 

I have been at this for more then 40 years and never ran into this problem before. The issue, as I see it, is that the array being used is set to 60 and then kicks up this error when it can’t place any more file names in the array. 

As for screens, I was under the impression that all were opened during a lookup as they are in the folder(directory) being used. I was not aware that close could be used to close all open files. I would rather close open files when finished with them (the end of a lookup or import).  I am not aware of any difference in how filePro handles opening files between *clerk and *report. 

Richard Kreiss
GCC CONSULTING 
Sent from my iPhone

> On May 19, 2021, at 11:33 PM, Ken Cole via Filepro-list <filepro-list at lists.celestial.com> wrote:
> 
> 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.