Steve, Yes, the field needs to allow for New Data/Change Existing Data. But since the cursor will always 'Skip' to another field it doesn't matter. In one instance I made this field the same color as the form and put it under another field (doesn't seem to matter) so the user could hit enter to exit the form (like a message screen). I think Karen originally posted the idea... the eep checked (lastkey(0)) to know what to do.
In a region I've been using a different technique lately. I color a variable field differently and text directs the user to "Click green" for more info. An eep sets that var to 'X' and skips. A second form is called by another eep. After processing, the 'X' is set to null and the user is returned to the region in the next field. In your case this might eliminate the need for using the intensity setting. Ben <<Ben, how does this technique work? I think I get the gist of what you're saying, that is, have a "trap" FIELD, that VAR FIELD you suggest, to prevent movement to another row w/o appropriate checking. However, doesn't a FIELD's SETTINGs require that either NEW DATA CAN BE ADDED or EXISTING DATA CAN BE REPLACE? Is there some "trick" to co-locating fields directly on top of one- another. Thanks, Steve in Memphis >> ================================================ TO SEE MESSAGE POSTING GUIDELINES: Send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: INTRO rbase-l ================================================ TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: UNSUBSCRIBE rbase-l ================================================ TO SEARCH ARCHIVES: http://www.mail-archive.com/rbase-l%40sonetmail.com/
