rob@xxxxxxxxx wrote:
When the user activates one of these fields will the appropriate
check constraints, and/or referential constraints, now take effect?
ie: Must be a valid date that is less than 125 years in the past
or some such thing?

Good questions. I didn't envision defining constraints with DDS or SQL, or generating triggers, but it seems that some level of data validation needs to be available. I do envision enabling users to define drop-down and popup selection lists, where list values are defined in other tables.

I did envision a flag in the field definition to indicate whether a value is required (non blank) or not. I was thinking about enabling range validation for numeric fields, but hadn't considered date range validation.

Thanks, for the suggestion.

Nathan.



As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.