>I have seen the problem, and it has nothing to do with the mouse.

You are right, if you substitute 'little' for 'nothing'.

>I had a form with some numeric fields, and when entering a new record, and use the TAB key to get into the field, when entering a one, then a period, then a decimal value, the value would end up being ten and the decimal (ie. 1.95 would end up 10.95).

The key is 'when entering a new record'.

>To keep this from happening, you'd have to enter the one, then the period, then hit the BackSpace key and hit the periosd again. Very annoying, and if you're a touch typist and not looking at the screen, you get a big surprise. I finally ended up putting some basic KEYBOARD commands in to fix it. (By the way, I did have the field defined as Select On Entry).

Totally unnecessary. See my message to Jim Booth as part of this thread, or just read the excerpt:

This situation has been with me since dBase days. When it showed up in FoxBase, I figured it was something I had to tell users to live with ... that is the way it is!

No more!

If, when creating a new record with insert into (and this may be true of append), give each numeric field a specific value (i.e. 0.00) rather than assume that it will be properly filled in if you don't mention a value (or in the case of append memvar, the variable has not been defined).