system command and dummy fields

[GCC Consulting]

> -----Original Message-----
> From: filepro-list-
> bounces+gccconsulting=comcast.net at lists.celestial.com [mailto:filepro-
> list-bounces+gccconsulting=comcast.net at lists.celestial.com] On Behalf
> Of Bob Stockler
> Sent: Monday, May 19, 2008 3:23 PM
> To: filepro-list at lists.celestial.com
> Subject: Re: system command and dummy fields
> 
> GCC Consulting wrote (on Mon, May 19, 2008 at 11:39:52AM -0400):
> 
> | Dennis,
> |
> | Who is controlling access to the record involved?  Do your screens
> have
> | passwords?
> |
> | Since you seem to be using a record to hold this data, one could add
> value
> | checking to processing to insure that no improper values appear.
> |
> | However, if one wanted to completely safe, the same logic should be
> added to
> | the output processing just in case someone figured out how to access
> the
> | record without any processing.
> [snip]
> 
> I can access filePro "key" files with a GAWK program.  It doesn't
> modify the record header when a field is edited.
> 
> Bob
> 
> --
> Bob Stockler +-+ bob at trebor.iglou.com +-+
> http://members.iglou.com/trebor


Bob,

That's why I suggested using filePro's file i/o to list the available files
and processing in list boxes.  This eliminates human entry and avoids
hacking a record problem.  One other possible solution would be to use and
ASCII file hidden somewhere on the system with the file & processing names
and reading them in.

Of course if one saves the processing tables in ASCII format, this would
make this method useless as someone reading the code could see where this
file is kept.

Richard