Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Automatically exiting a textbox control when it's full
Message
From
31/12/1997 12:20:10
 
 
To
31/12/1997 11:55:48
General information
Forum:
Visual FoxPro
Category:
Coding, syntax & commands
Miscellaneous
Thread ID:
00068171
Message ID:
00068653
Views:
42
Ernie,

Look in the VFP Help - Each SET which "Scopes to the current data session" says so somewhere in the body of the writeup. There is also a list somewhere in Help which lists them all.

By the way, "scopes to the current data session" is sort of code for 'must be set explicitly for each data session'.

Sounds like this is the source of your "problem".

Jim N


>>>>Ernie,
>>>>
>>>>Adding to what Barbara said. . . you must also ensure that you have CONFIRM set OFF.
>>>>
>>>>Cheers,
>>>>Jim N
>>>>
>>>>>>Is there a property that can be set *somewhere* that will globally cause the cursor to exit a textbox field when the maximum amount of data allowed has been entered? You know, say a phone number with 10 digits ... after the 10th digit is entered, I would like the cursor to move to the next control. (Pretty common, but for the life of me, I can't find what makes that happen.)
>>>>>>
>>>>>>Please and thanks.
>>>>>
>>>>>Ernie, check the FORMAT and INPUTMASK properties of the textbox control. You should be able to handle everything you want with these - telephone numbers, social security numbers, etc.
>>>>>
>>>>>Barbara
>>>
>>>Thanks for your input. I've tried playing with FORMAT, INPUTMASK, MAXLENGTH, and making sure SET("CONFIRM") = OFF but I'm still having trouble making this work. I must still be missing something. Inputmask is (999) 999-9999, Maxlength is 10, and Format is KZ. Could there be an overriding property elsewhere? Baffled.
>>>
>>>Ernie
>>Hi Ernie,
>>Two points :
>>1. In format mask you use KZ. Z for zero, is this a numeric value ? For tel. numbers it's convenient to have char values and format mask as KR.
>>2. SET CONFIRM is scoped to current datasession. So if globally you have *set confirm on* and you set it on entry.prg *off* it won't *set confirm off* in form loading with a DE. It will be set back to *on*. In DE, beforeopentables event add *set confirm off*
>
>Wow, I was always under the impression that Form.Load was where we should set up the SET options. What other
>SET options are reset to default after Form.Load? Or maybe I should move all of them to BeforeOpenTables?
>
>Bill
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform