Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
SET POINT and numeric input
Message
 
To
11/01/2002 06:47:32
Hilmar Zonneveld
Independent Consultant
Cochabamba, Bolivia
General information
Forum:
Visual FoxPro
Category:
Coding, syntax & commands
Miscellaneous
Thread ID:
00603396
Message ID:
00603404
Views:
18
>Users typically input lots of numbers with the numeric keypad, but when the Control Panel defines the decimal "point" as a comma, the point is not accepted. This is awkward for quick data entry.
>
>Does anyone have a satisfactory solution for this? I want to continue using SET SYSFORMATS ON. I think several approaches are possible in theory, including a) temporarily changing SET POINT for the control that has the focus (how?), b) converting commas to points in .KeyPress().
>
>TIA, Hilmar.

Hilmar,

Here in Holland we have the similar with our notation of 1.000.000,25
"In the beginning" I tried to solve this and gave up;
VFP seemed to give more opportunities and I tried it again to no avail.

Right now I am not really sure anymore what the anomalies were, but they are there; the comments in the according program here state that there are (will be) all kind of problems with the typing of numerical controls.
But maybe I didn't find the right combination.

Keywords :

SET POINT TO
SET SEPARATOR TO
ON KEY LABEL ... PLAIN
KeyPress

I remember that I gave up, knowing (or finding out) that somehow we do type a dot for the decimals separator like on any general calculator. So, I quit this task really for another reason. However, I think you will find yourself in trouble looking at the dot in a numerical which just will remain. I mean, I don't think that can be changed, and with ControlSources etc. this will be fighting you forever.
But maybe others have the solution, though the community on this is relatively small I think; who will need it ? us overhere possibly, and a handful other countries ? But it's interesting though.

In our app we have (dependent on the country) SHOWN all like we are used to by a custom function. So 100.000,25 for us and 100,000.25 for UK (etc.). Not doing this will make things really unreadable to the according countries, thinking of 100,250 vs. 100.250 when the system uses three decimals a lot (like ours for weight and more).
The controls for input never have the thousand separator in them, and always the dot for the decimal separator; there was not any complaint so far because -again- somehow overhere we do like to type the dot (but strangely we can't read it back like that).
The integring things of life.

I'm not sure how your situation is (and why the control panes defines as is), but maybe this helps a little.
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform