Re: 4GL required keyword

Steve, You're much safer using the include attribute. For states - include=("NY","NJ","TX", .... For numbers - include=(0-100) or For years - include=(1980-2100) Well, you get the idea. Later, At 04:42 PM 4/24/00 -0700, steve farris wrote: Hello, I'm trying to use the "required" keyword to insure that a user fills out all necessary parts of a form when entering data. However, they are able to hit escape before entering all information which causes a improper null value crashing the update. I am using something like: entry.per: ====== database test_regs screen size 24 by 80 { State [a0] Number [f000 ] Calendar Year [cy ] } tables regs_actions attributes a0 = regs_actions.state,upshift,required; f000 = regs_actions.number,required; cy = regs_actions.calendar_year, upshift, required; end Shouldn't the required cause the form to inform the use that they MUST enter a value in these fields?? Thanks! -- steve farris nylon fusion guitar site at http://www.mindspring.com/~nlymbo Mark Griebling mailto:mgriebling@acm.org