Two parter: rant & wishlist items

[Mike Schwartz-PC Support & Services]

> From: filepro-list-bounces at lists.celestial.com [mailto:filepro-list-
> bounces at lists.celestial.com] On Behalf Of Walter Vaughan
> 
> "auto.prc" or "prc.automatic" processing tables are probably taught way
> too early in a filePro developers life. When you use them, they should
> come with a warning label that says, "You know that every record from
> now on in this file will execute this processing table twice per record

Hi Walter:

It gets even more dangerous (or useful, depending on your point of view),
because programmers can use the -Y option to use any other processing table,
or no processing table at all, as the automatic table.

I spent a couple of hours last week trying to debug some code in an
automatic table, only to find out that the programmer was still using a
system command to call dclerk with -Y set to "test1", even though test1 had
been written over 10 years ago!  (I'm glad I didn't just go through the
filePro files and blow away all the old "test" and "junk" processing
tables!)
  
I like the variable checking that filePro does against the "auto.prc" table
when you leave another processing table.  However, I don't know how filePro
could possibly check the variables in the table I am writing against every
other processing table in the file.  

Mike Schwartz