ignoring a and b drives

[Bob Stockler]

On Thu, Apr 29, 2004 at 01:36:59PM -0400, Jay R. Ashworth wrote:
| On Thu, Apr 29, 2004 at 01:41:14PM -0400, Bob Stockler wrote:
| > | > ForEach DRIVE in $PFDSK
| > | > do
| > | >     using $DRIVE/$PFDIR/filepro/$PFNAME
| > | >     do
| > | >         LookFor key*, data*, index*
| > | >     done
| > | > done
| > | 
| > | IOW, it's looking for your current PFDIR underneath those drive
| > | letters/directories.  I assume that a) it scans them in order, and b)
| > | it stops scanning the first time it finds a valid PFDIR under one?
| > 
| > I'd guess "a" is correct, but it doesn't matter, because
| > in-so-far as "b", it scans all of them to find all of the
| > filePro files in the $PFDIR/filepro directories under them.
| > 
| > That's what lets one have the programs relating to a filePro
| > file on one HD, the key file another, the data file on another,
| > and the indexes on yet another, if one wanted to split them up
| > that much.
| 
| Which means that if you have multiple PFDIR's under PFDSK, filePro
| directories in those PFDIR's with identical names will be treated as
| merged.
| 
| But, does it also merge the lists of filePro directories from all of
| the located directories, presenting them all as one list? More
| importantly, what if you have multiple PFDIR's in one PFDSK with the
| same name but *different* data (and complete complements of files)?
| 
| Will they collide?  Loudly?  When you try to use them, or at scan time?

I don't completely understand your question, so I'll avoid
it and hope to clear the matter up this way:

  PFDSK=/u:/u1:/u2
  PFPROG=/u/appl
  PFDATA=/u
  PFDIR=/appl

filePro will expect to find its programs in /u/appl/fp.

filePro will expect to find filePro Files and their formats
and programs in $PFDATA$PFDIR/filepro.

filePro will look at:

  /u/appl/filepro
  /u1/appl/filepro
  /u2/appl/filepro

for filePro Files.  There may be one instance of any or all
filePro Files in any one or all of these locations.  The key,
data, and any index files belonging to any filePro File may
be in any one of them, but not in more than one of them.

You can have as many different PFDIRs as you want in any of
them, but filePro looks only at the one it knows about when
it starts up.

Bob

-- 
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).