Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. Mouse is unresponsive in Visual Studio Tools for Microsoft Dynamics GP modal window

Mouse is unresponsive in Visual Studio Tools for Microsoft Dynamics GP modal window

Symptoms

The symptom of this bug is that as soon as the issue occurs, the user is no longer able to click into any field in a modal .NET window.  The reason for the included DexVBA.dll is to resolve bug 54378 before Dynamics GP SP5 is released.

The nature of the bug is a combination of a .NET window (typically a GP Addin) displayed as modal and having VBA active in Dynamics GP. When this happens, it prevents the user from clicking any field in the .NET modal window until they exit Dynamics GP. The user is still able to tab, use character keys, and so on in the window. This issue only affects Dynamics 10.0 SP1 to 10.0 SP4

↑ Back to the top

Cause

The cause of the issue is a conflict between a .NET event loop that manages the .NET Framework application windows and our internal event loop to manage the interaction of a VBA modal window and Dynamics window.  When this issue occurs, the VBA event loop is obtaining the mouse clicks and disposing of them instead of the .NET window.

↑ Back to the top

Resolution

The resolution to this issue before Dynamics 10.0 SP5 is released is to install the DexVBA.dll from theMBSGreatPlains_54378.zip file that you can download here.  The zip includes instructions about how to install the DexVBA.dll.

↑ Back to the top

More Information

When you upgrade to Dynamics GP SP5, this version of the DexVBA.dll will be overwritten with the SP5 version.  Dynamics SP5 will contain this same fix and therefore this interim solution will no longer be required.  This fix will also be included in the 11.0 RTM release.

If this .dll file is deployed to a pre-10.0 SP4 installation and then upgraded to a pre SP5 service pack, the .dll file should not get overwritten with an older version.  For example, if the current installation is currently 10.0 SP2 and this fix is applied, updating to 10.0 SP4 should not overwrite the newer DexVBA.dll included in this fix. However, if after an upgrade you see the mouse issue reoccur then verify that the DexVBA.dll is the 10.0.327 version from this fix.  If the file version not 10.0.327, then reapply the DexVBA.dll by using the steps from the Deployment section earlier.

If you have to do a Repair on your Dynamics GP, it will not remove the new DexVBA.dll v10.0.327 that this hotfix includes. The installer has built in logic so that it will not replace the newer version of the .dll file that has the older version that is built into the current installation.

 

↑ Back to the top

Keywords: kbmbspartner, kbmbsmigrate, vkball, kb

↑ Back to the top

Article Info
Article ID : 2011612
Revision : 1
Created on : 1/8/2017
Published on : 8/15/2012
Exists online : False
Views : 235