djgogi Posted March 20, 2003 Posted March 20, 2003 How to prevent creation of additional lines . Well, it's all that simple that I can't imagine why I didn't find it before. OK, it's an workaround, but until FMI don't give use option to limit data entry into field to only one line... Check the attachment. Dj OneLineField.1.zip
Newbies Mickster Posted March 24, 2003 Newbies Posted March 24, 2003 Hi DJ, Nice little trick! I see how the look up is structured. But why does the field called "text" accept a carriage return on the "description" layout (but not on the OneLineField layout). Also, if you create a new "text" field on the OneLineField layout you can out a return. But not if you copy this field on the same layout. I couldn't find anything in the format! Creating a "text" field by using the self-relationship to ntext does give that new field the protection. This could help to quickly identify protected vs. non-protected fields, thought there might be a performance penalty if there are many records (?) Thanks for a nice solution. Still scratching my head! Michael.
djgogi Posted March 24, 2003 Author Posted March 24, 2003 The "field" text, on "no returns" layout is group of 2 fields, ntext and text , with "text" above and disabled field entry. Dj
Newbies Mickster Posted March 24, 2003 Newbies Posted March 24, 2003 It all makes sense. I noticed the two fields were grouped. Thanks.
Helpful Harry Posted March 25, 2003 Posted March 25, 2003 Nice trick, but it doesn't quite work properly. When you create a new record and type in some text, then you exit the record and the "field" goes blank (ie. the top field stays empty). Click in the field and your text comes back for editing. If you modify the text THEN the "field" updates to the changed text.
djgogi Posted March 25, 2003 Author Posted March 25, 2003 You see, I don't create solutions where users are permited to create records (or delet or perform find) from menu, so the simple script like: New record/Request Exit record/Request will just do the job. Dj
djgogi Posted March 26, 2003 Author Posted March 26, 2003 Yesterday I was in hurry, so I didn't have time to think about it. The problem is to allow null entries, iow if you clear ntext the text field should clear itself automatically. The other possible solution is to omit ALL fields from tab order, so that newly created record will commit immediately. In this case no scripts are required at all, and the behavior is what expected, when you clear the ntext the text field is cleared too. Dj
Recommended Posts