bb.donnay-software.com

One of our clients is reporting that the cursor is skipping to the next field while they are typing. this is on both text and numeric fields. it is not happening all the time, but has only started since the 1803 update. I connected with gotomypc, but it would not do it while i was connected. It's happening on multiple machines with multiple operators.

just throwing it out there to see if anyone else has come across this...

this is xbase 2.0 875 with the windows 10 creators version fixes.
express 265

What do you mean by "skipping to the next field" ?
Is this in a screen of GETS?

yes, in a screen of gets, they start typing and the cursor jumps to the next get in the middle of their typing..

so, if they are typing smith, the sm may go into the original field, but the ith goes into the next field.

no consistency or pattern to it..

Is this a laptop with a mousepad? Maybe "lazy thumb" syndrome?

Apparently, either CR or TAB characters seem to be getting processed.

Turn off TABSTOP to figure out which.

A sticky TAB or ENTER key maybe?

I don't see this problem on my computer. Same Win 10 version.

We're not seeing it at any other clients either.. It just spring up in conjunction with the 1803 win10 release. they have been a client for quite awhile, so if it was accidental keying, it would have done it with earlier versions.

multiple users, multiple computers...

I just wanted to see if anyone else had come across it..

is it a (old) Bluetooth Keyboard

usb keyboard. desktop not laptop.
windows 10 pro

Tell the customer to buy a new keyboard.

multiple computers... no issue before 1803.

We've gotten some more information from another client...

This client is on windows 7 and we're not sure if it's the same issue. but it probably is..

The cursor is NOT skipping over fields... what seems to be happening is the cursor is not always going to the start of the first field when "A" for add is pushed. sometimes it ends up in the middle or at the end of the field. So, when the user starts to type, instead of having 8 characters (the length of a sample first field) before they reach the end of the field, they might have 1, 2 or something less than 8..

This is the first explanation of this issue that makes sense to me.. it's probably something that changed in xbase or express that's incompatible with our standard key handling...

I can't make it happen on my machine, and will be unable to remote into the client until next thursday...

further information to follow as gathered..