You can't do that

[Scott Brown]

>
>John, you are lucky that you have not been exposed to
>the garbage that I have seen :-)
>
>It also seems that you are getting lost with just this
>one example.  My request was for rules for data
>integrity.  This would just be one of the possible
>rules.
>
>Example: I have seen many situations where the
>programmer has allowed the deletion of a record such
>as an an inventory record, when it is still referenced
>in another file such as an order file. Ouch.
>
>Some other possible rules would be:
>
>Force certain field(s) to be unique.
>Require a non-blank field.
>Require the existence of a matching record in another
>file.
>Minimum/Maxium values for fields.
>Math rules for field values. (Ex. Field must be an
>even number)
>Prevent any records from being deleted.
>Require that if field A is filled in then field B not
>be filled in.
>
>These are just a few of the possibilities that come to
>mind.
>
>Jeff Harrison
>jeffaharrison at yahoo.com


I for one, would hope that FilePro would not put these kind of limitations 
on their software. Most of what you mentioned should be taken care of by the 
person writing the program. It's not FilePro's fault if some programmers 
can't write good code.

Just my humble opinion,

Scott....