How do I stop a user from moving to the next prompt (OpenInsight 32-bit Specific)
At 30 MAY 2006 12:50:31AM dave w bennett wrote:
I am creating a validation routine in the lost focus and need to stop the user from moving to the next prompt
At 30 MAY 2006 02:46AM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote:
Use the FOCUS property. See the on line help for which one is most appropriate for your purpose.
World leaders in all things RevSoft
At 30 MAY 2006 03:25AM dbakke@srpcs.com's Don Bakke wrote:
Dave,
Is there a reason you aren't creating a user-defined validation instead?
dbakke@srpcs.com
At 30 MAY 2006 11:30AM dsig@sigafoos.org wrote:
]]I am creating a validation routine in the lost focus and need to stop the user from moving to the next prompt
In the old days .. The Shick Centers would wire the user and give electro shock when the user moves to the 'field' (they said it worked for smoking :)
No .. not using that method (though it would be fun) I would suggest setting controls DISABLED depending on user. Getting things set up to begin with has always worked better for me.
What are the rules for CONTROL X?
At 30 MAY 2006 12:11PM Gerald Lovel wrote:
Don's response suggests a certain line of thinking. AREV handled certain validations as post-prompt processes, where setting VALID and RESET prevented the user from moving to another control. This form of prompt validation is not supported in OI, which is one of the hinderances to porting. Don is suggesting that creating a user validation/conversion is the preferred OI methodology, and I concur.
OI throws another wrinkle in the validation/conversion because the routine may be performed three times on input – once for validation, once for input conversion (to create INVALUE), and once for output conversion (to display text). I usually program my conversion routines so that the branch consists of "V|branch" for validation and "F|branch" for window form conversion. Where a straight ICONV/OCONV is required, the "V|" or "F|" would be omitted.
Using this logic, a user conversion in OI could consist of 5 internal parts: ICONV validation, ICONV form conversion, ICONV data conversion, OCONV form conversion, and OCONV data conversion. The number of actual parts to each routine depend on the specific requirements of a conversion, of course. I believe the use of Status() to indicate conversion success and failure differs markedly between AREV and OI too, but I will leave that for another discussion.
At 30 MAY 2006 12:13PM Gerald Lovel wrote:
Must be having a bad beard day. However, I heard how this would work for politicians. Wire a lie detetector to an electric chair. Instant truth in politics. No more politicians.
Uh, maybe we should all get back to programming.
At 30 MAY 2006 01:16PM dsig@sigafoos.org wrote:
what the *^%% are you talking about ..
why don't YOU get back to programming ..
At 30 MAY 2006 01:25PM dsig@sigafoos.org wrote:
Dave ..
as i alluded to before it might be best if you could expand what you are looking for .. there have been 3 basic suggestions and 1 rehash of a suggestion.
So as you can see .. there are many ways to do things .. but sometimes the optimal way comes from completely understanding the rules.
is this just 1 column?
is this just 1 user?
is this just for this window?