Re: next field problem
Posted in 1995
i've considered this, but it won't help for all the fields: one of the fields requires a value that exists in another table, and does a "lookup" to that table. -joe- (huddles@hasting.com) ---------- From: ilist To: informix-list Subject: Re: next field problem Date: Tuesday, March 14, 1995 5:09PM Another thing to consider is putting the value constraints in the .per rather than checking in the code. Simply use the "include" statement to enforce the validity of data entered. You can use the "comments" statement to inform the user of what the acceptable values are. -- Carlton Doe "It's not *over* until I win!" DBA Resources, Inc. -- Les Brown Salt Lake City, UT carlton@errin.dbaresrc.com http://xmission.com/~dbaresrc