Weird Tabbing Seq and ACCEPT key
Posted in 1993
I've noticed some unexpected behavior when trying to INPUT BY NAME a cursor'd record within a form that has a fairly large (~22) number of fields that have been AFTER FIELD ... NEXT FIELD'd so that the order entry sequence makes sense (the table itself is not in order entry sequence, hence the instructions). Whew! [The underlying code itself is based mostly on db4glgen-created code.] The unexpected behavior is that instead of "adding a row", when ACCEPT is pushed, the cursor will go to a field (Note, I don't have a REQUIRED keyword for any of the fields in the [per]form). Continuing to press the ACCEPT key will cause the cursor to tab through an inner circle of most of the fields but not all (eg, the table indexed field is not entered). I can get to all of the fields by pressing the <return> key. Once is a while, if 2 ACCEPT keys are pressed quickly, a row will be added. Most of the time if I <return> to the field the table is indexed on and then press ACCEPT, a row is added. I have checked to make sure the AFTER FIELD .... NEXT FIELD sequence is circular. I've played around with commenting out the NEXT FIELD instructions, in data entry order, only to find out that ACCEPT works OK for about the first five fields, then starts to display these symptoms. BUT, every so often as I comment in the NEXT FIELD instruction for that field, the program will add a record simply by pressing the ACCEPT KEY. Weird. Anybody have any clues or pointers where I should be looking next? Marc Ries