DCGET behaviour

[reganc]

This may or may not be an Express++ problem...

We had a customer phone telling us that something strange was happening in their system and they explained it as below:

In an entry field (a DCGET) that allows entry of a number of 9 digits including two decimal places, they highighted the entry field so that the last 5 digits including the decimal point (in this case, this was because the value in the field was 49.99). They then typed a single number (4 in this case) and that worked as you would expect but as they typed the second number (5 in this case) the first digit (the 4) disappeared and the cursor went to the left of the field at position 1 and the second digit (the 5) was shown (eg, if they typed 45, they ended up with '5xxxxxx.xx' where the x's are spaces).

It is not a big issue but is a little odd...

Does anyone have any thoughts about this? Does everyone see the same thing happening in their systems (if you can reproduce it based on my crap description above...)?

[omni]

I have seen similar keying with scroll lock and insert key not set right. Different mother boards can do different keying based on chipset,etc.

Fred
Omni

[rdonnay]

I think it may be an Xbase++ / eXpress++ problem based on the behavior of the Get() class from which DC_XbpGet() is derived.