Customer called in regards to a problem he was having with his application.
His application uses Swing components and the ActiveX bridge. Customer's
complaint was that his dialog box would not receive input from the user
if used as an ActiveX component. However, things worked fine within
the standard beanbox supplied with the BDK.

Further investigation shows that the problem seems to arise if the
JDialog is a modal dialog and is 'popped' from another ActiveX
component.

I installed Microsoft ActiveX Control Pad in order to use
JavaScript to call a method which pops up the customers modal dialog.
This does indeed lock the process. It seems that the calling
thread does not liked to be blocked by this dialog.  However, using 
a non-modal dialog works fine.

Modal's seem to work fine if called from within the Component requesting
the modal box. For example, one of my testcases was a JPanel with
a button which instatanted a Modal Dialog. This worked. However,
if I attempt to instantiate this modal from another ActiveX component,
the application hangs.