I've recently tried out some of the DBC features to preserve data integrity: (1) candidate indexes to ensure that fields are unique, and (2) record validation rules. These rules work fine in browse windows; if a rule is violated, a message appears giving you the revert option (actually, you don't have a choice, you HAVE to revert, so it really shouldn't be an option). However, if a user violates these rules entering data on a grid in a form, you get an error message with options to "Cancel, Suspend, Ignore"; none of these options solve the problem--which must be a table revert. Also, I don't know how to write an error handling program that will do an automatic revert; if you have a screen for data entry into tables that are related, you have know way of knowing which table to revert, and there are no error parameters that can give you this information. I have concluded that I should get rid of these candidate indexes and record validation rules and handle everything in the form. This is unfortunate, because there is no row-validation method for a grid that I know of that can take the place of record validation rules in the DBC.

Anyone have a better solution?

Thanx,

Linda Swift