Commands Possibly Using filePro File Names

Bob Stockler bob at trebor.iglou.com
Wed Mar 30 18:42:29 PST 2005


On Wed, Mar 30, 2005 at 07:39:40PM -0500, Ken Brody wrote:
| Quoting Kenneth Brody (Wed, 30 Mar 2005 19:32:18 -0500):
| 
| > Quoting Bob Stockler (Wed, 30 Mar 2005 17:44:27 -0500):
| >
| > > I've identified the following filePro Processing Table Commands
| > > as those possibly having filePro File Names in their arguments:
| > >
| > >   CALL, CHAIN, CLOSE, COPY, COPYIN, COPY_TO, DELETE, DIM, FIELDEDIT,
| > >   FIELDLEN, FIELDNAME, FIELDVAL, GETNEXT, GETPREV, LOCKED, LOOKUP,
| > >   NUMFIELD, POPUP, POPUP_UPDATE, SYNC, WRITE
| > >
| > > Have I overlooked any?
| >
| > NUMRECS(), OPENDIR() come to mind.
| 
| Well, technically, most of the above take a lookup name, not a file
| name.  (Though CALL, CHAIN, LOOKUP, and OPENDIR do take file names.)

Thanks.

While most of them are associated with LOOKUP, it's possible
that the LOOKUP doesn't use an alias, so all are significant.

I'm writing an AWK program to edit/change the filePro File Names
in all processing tables on a system, and wanted to save time by
not working on Processing Table lines where a filePro File Name
would not be of interest.

This information lets me build a regular expression allowing me
to skip processing all lines where fPname1 won't possibly be
required to be changed to fPname2.

Bob (Stockler the Timer - and Consevator of Time)

-- 
Bob Stockler - bob at trebor.iglou.com
Author: MENU EDIT II - The BEST Creator/Editor/Manager for filePro User Menus.
Fully functional (time-limited) demos available by email request (specify OS).


More information about the Filepro-list mailing list