Re: Need help with referencing fields within a construct

Jonathan Leffler wrote: > As long as you don't mess with OPTIONS FIELD ORDER UNCONSTRAINED, > your analysis should be correct. Oh, and there are other conditions too, such as there > is a field after the last field to be skipped, and a field before hand, and there's more > than > one field to skip. Lose any of those and life becomes a whole heap harder. Been there; > done that; codified the results; have forgotten the details but know where to go to find > them. I've got all of those bases covered. I'm doing it the simple way. Of the four fields, condition A allows you into the first two, skipping the last two and condition B allows you into all four, while condition C skips all four. I always have at least two fields being skipped so that the before field becomes the simplest method and I don't have to test for what keys were pressed or anything that might stress my aging brain cells. I do appreciate the heads up though. I know enough to know that I don't know enough, so I don't mind when someone points out something I'm already aware of. Things that are quite obvious to you may not be to me. In this particular instance I was not even aware of the get_fldbuf() function's existence. I could have deployed the program without the field skipping, but (thanks to you and June) was able to send out a much more user-friendly version that's been in place since last Thursday to rave reviews. Thanks for helping my cape to blow in the wind...... > If you ever get really brave, you can write code to do seamless wrapping across three > forms, > so that when you go up from the first field on the third form you end up in the last > field on > the second. That's really rather tricky! I don't think this project is quite that ambitious, but you have piqued my curiosity. I hadn't even thought of doing something like that (so much for creativity points on my part) but now I probably will be thinking of applications. carlos -- ------------------------------------------------------------------------------- Carlos Benjamin, Jr. (623) 869 - 2364 Programmer/Analyst/Consultant Currently Assigned to Central Arizona Project mailto:inf999@cap-az.com -------------------------------------------------------------------------------