Re: un-freaking-believable

}Subject: Re: un-freaking-believable }Date: Sat, 9 May 92 16:33:49 EDT }X-Informix-List-Id: <list.1158> Quoting Dave Snyder... }Quoting Mukesh Rathor... }> }> I have a screen driven by 4gl to I/O in customer and contacts tables. }> On the screen is field customer.phone_no. I added field }> contacts.phone_no on the screen at the bottom. Upon add in contacts }> table (input by name contact_rec.field1, ..contact_rec.phone_no....), }> the cursor instead of going on the contacts.phone_no actually goes }> up to the customer.phone_no. }> What is this world coming to!!!!!!! }> }To the best of my knowledge (someone will correct me if I'm wrong), you can't }use an INPUT BY NAME in a screen that has two or more fields with the same }name. You must use the INPUT variable-list FROM screen-record.variable-list }syntax. I'd agree with David, and I'd add that having a screen record in the instructions section seems to be enough to throw NEXT FIELD into fits if you use INPUT BY NAME. The best circumvention for the trouble is to always use INPUT variable-list FROM screen-record.*, if necessary creating an extra screen record just for the purpose. Most of my production forms have three screen records defined in the instructions section: s_input for the input fields, s_query for the CONSTRUCT fields (usually a superset of the s_input fields), and s_display (for any looked-up values displayed during input, typically equivalent to (s_query - s_input)). Yours, Jonathan Leffler (johnl@obelix.informix.com) #include <disclaimer.h>