I have a process that a user goes through maybe 30 times a day. The steps are always the same. During the process the sequence goes through 4-5 forms being displayed and allowing keyboard entry before a report prints from each form. This happens at literally hundreds of locations with no problems and no issues. However, on all of the machines at one single location a strange thing happens. When the user goes to a form and the form displays, all of the fields will be accessible but the cursor dissappears. Clicking in any field on the form the user can type but the cursor is not visible. The strangest thing is that no matter what key the user presses on the keyboard, the
(ctrl+F1) key is the result (a 'y' with the two umlauts on top of it) in all fields. Now, the titlebar of the form itself actually appears disabled, but the form is not disabled.
**The REALLY strange this is that when the form initially displays and appears deactivated for some reason, if the user presses the windows key on the keyboard (which activates the startmenu in windows) and then clicks with the mouse on the titlebar of the form in Visual FoxPro, everything returns to normal and the titlebar is now dark, the keys work correctly in all fields, and the cursor is active. Once this problem occurs, it happens everytime until I delete the resource file and restart our app (or so it appears).
All of the systems are new systems.
Windows XP.
6 workstations.
I have checked the power settings, desktop themes, resource files, other Visual FoxPro apps and their files, replaced the keyboard, etc. It will only happen at this site and then it is reproduced nonstop.
Any ideas? Why does switching tasks to/from windows startmenu fix it? The form is the same form that has run for years (and called in the same sequence) by hundreds of users.
Not using a resource file does not resolve this error.
Thanks in advance
(ctrl+F1) key is the result (a 'y' with the two umlauts on top of it) in all fields. Now, the titlebar of the form itself actually appears disabled, but the form is not disabled.
**The REALLY strange this is that when the form initially displays and appears deactivated for some reason, if the user presses the windows key on the keyboard (which activates the startmenu in windows) and then clicks with the mouse on the titlebar of the form in Visual FoxPro, everything returns to normal and the titlebar is now dark, the keys work correctly in all fields, and the cursor is active. Once this problem occurs, it happens everytime until I delete the resource file and restart our app (or so it appears).
All of the systems are new systems.
Windows XP.
6 workstations.
I have checked the power settings, desktop themes, resource files, other Visual FoxPro apps and their files, replaced the keyboard, etc. It will only happen at this site and then it is reproduced nonstop.
Any ideas? Why does switching tasks to/from windows startmenu fix it? The form is the same form that has run for years (and called in the same sequence) by hundreds of users.
Not using a resource file does not resolve this error.
Thanks in advance