We're in the process of integrating our current Visual Basic projects to run under a Windows2000 environment. The main application creates and uses a Word object, which has custom pull down menus and a custom Function key toolbar. Unfortunately upon Word becoming available to the User, the Mouse is totally unresponsive (left and right buttons are inactive), and the keyboard fails to activate any of the pull down menus. However, the Function keys are the only thing to work.
Typing in the Word doc itself is also possible.
The pull down menu is 're-activated' by choosing the appropriate Function key that will either open a form or show a message box, whereby the menubar works normally.
Has anyone else experienced similar quirks running apps under W2K? Now, not all keyboard functions are lost; selecting 'Alt-Q', (which is pre-defined) for example functions correctly, but selecting the normal 'Alt-F' to pull down the File menu fails to operate initially.
I also seem to lose 'focus' on a just opened form where the only way to use it is to first click on the form itself with the mouse.
Jim
Typing in the Word doc itself is also possible.
The pull down menu is 're-activated' by choosing the appropriate Function key that will either open a form or show a message box, whereby the menubar works normally.
Has anyone else experienced similar quirks running apps under W2K? Now, not all keyboard functions are lost; selecting 'Alt-Q', (which is pre-defined) for example functions correctly, but selecting the normal 'Alt-F' to pull down the File menu fails to operate initially.
I also seem to lose 'focus' on a just opened form where the only way to use it is to first click on the form itself with the mouse.
Jim
