Greetings to the well of knowledge...
This is a strange one.
I have a user of one of our Access front-end apps that often has need to move from an app that requires data entered as all caps (primitive, I know) to the Access front end. There is a drop-down search field that users can employ to select an individual. I cannot describe what's going on but I can show you video.
Here are links to two videos in my Google Drive:
This one shows the correct behavior for this drop-down object: Correct behavior
This one shows the bad behavior that this user is seeing: Bad behavior
Note that Caps Lock is on for both scenarios.
I have looked at the properties of the field and see nothing amiss. And here's the other thing: I use this same logic in other drop-down fields, and it works as expected for everyone, including my problem user.
I've recompiled the front end, thinking it might have become corrupted.
I've replaced the keyboard.
I've moved the keyboard to a different USB port.
No love.
Frankly, I'm thinking there some kind of flaw in either Windows, this person's copy of Access, or the hardware.
Any thoughts?
Thanks,
Ken
This is a strange one.
I have a user of one of our Access front-end apps that often has need to move from an app that requires data entered as all caps (primitive, I know) to the Access front end. There is a drop-down search field that users can employ to select an individual. I cannot describe what's going on but I can show you video.
Here are links to two videos in my Google Drive:
This one shows the correct behavior for this drop-down object: Correct behavior
This one shows the bad behavior that this user is seeing: Bad behavior
Note that Caps Lock is on for both scenarios.
I have looked at the properties of the field and see nothing amiss. And here's the other thing: I use this same logic in other drop-down fields, and it works as expected for everyone, including my problem user.
I've recompiled the front end, thinking it might have become corrupted.
I've replaced the keyboard.
I've moved the keyboard to a different USB port.
No love.
Frankly, I'm thinking there some kind of flaw in either Windows, this person's copy of Access, or the hardware.
Any thoughts?
Thanks,
Ken