Re: Weird Tabbing Seq and ACCEPT key

In article <1993May24.181036.13365@venice.sedd.trw.com> ries@hqrim.sedd.trw.com (Marc Ries) writes: } 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.] } I'm not going to explain your program's weird un-expected behavor, but I will ask you a question... Why do you have all that BEFORE/AFTER FIELD stuff in you code to make the cursor go from field to field? By expanding the "INPUT BY NAME w_record.*" TO "INPUT BY NAME w_record.col1, w_record.col2, etc." you can control the cursor movement without all the BEFORE/AFTER FIELD overhead. You'll definately save brain cells when it becomes necessary to maintain the code. From your letter I'm guessing you have an older version of db4glgen laying around. The 3.12 version of db4glgen now has the CONSTRUCT BY NAME, INPUT BY NAME, and DISPLAY BY NAME clauses expanded for you so that re-arranging them is easier. Good luck with you project! DAS -- David Snyder @ Snide Computer Services - Folcroft, PA Current Release is db4glgen-3.12 UUCP: ..!uunet!das13!dave INTERNET: dave.snyder@snide.com