You can't do that

[John Esak]

> >
> > I said nothing about removing the edits. that's
> > putting words into my mouth
> > and is a really stupid statement,  maybe it would
> > have been better stated to
> > say that I don't think it would provide anything
> > that isn't able to be done
> > already when written correctly and why add more
> > unnecessary features.. just
> > my personal opinion..
> >
> > Scott....
> >
> >
>
> Of course you said nothing about removing edits.
> Brian was just trying to give you an example of a
> place where filePro currently has rules for data
> integrity.  It does not take anything away from
> filepro that these rules are available.
>
> Because it is possible to manipulate the data in
> processing the same way as in edits, It could be
> argued that edits add nothing to filepro so why are
> they there?
>
> In my opinion this is not a stupid statement nor is it
> putting words in your mouth.
>
> Jeff Harrison
> jeffaharrison at yahoo.com
>
> Author of JHExport and JHImport.  The easiest and
> fastest ways to generate code for filePro exports and imports.
>

All right. Allowing that the comment may not be stupid... both it and your
agreement with it are still easy to disagree with...  Your foundation for
the argument and using taking away edits as the analogy is confused. The
proper analogy if you want to use edits, would be not to take them away...
but to add another level of "rules" to the edit language. Then you would be
comparing apples to apples... the other comment was pretty ridiculous and I
can see where Scott would think it so.  Adding more complexity to edits
would certainly not help anything. As for the rules you suggest adding to
filePro somewhere... it sounded originally like you meant the processing
table area... I'll let my previous statement stand that this is not a
reasonable place for them and there is no existing place for them since
there is no overviewing structure to a group of tables. Currently, as you
know, filePro tables are not related in any way... solely through lookups
can there be some association and/or grouping. filePro is a "flat file"
system... which would be analogous to free-tables in other RDBMS systems.
And they, too, by the way, would have no rules that interplay between
themselves because free tables are "outside" of a database container.

I think asking for this is like asking for primary key joins in filePro. It
is simply not going to happen. Why not shoot for things that CAN happen and
would enhance the product?

John Esak
Visit The FP Room www.tinyurl.com/97y9u 24/7

Author of:
The filePro Survivor Series
Complete video training for filePro on CD.
See samples at: www.valar.com/training