Having problems with your account or logging in?
A lot of changes are happening in the community right now. Some may affect you. READ MORE HERE

When testing a VB Application locally it works, why then does it fail when run remotely?

When testing a VB Application locally it works, why then does it fail when run remotely?

The problem is that on the remote machine there is an additional layer being added. To remove this additional layer it is required to modify axext.ini.

  1. Open the axext.ini file and go to the[VBOptions] section
  2. Set AxextDelay equal to "number of seconds". It is recommended to set this to 30 seconds, however it may have to be increased or decreased depending on the application under test. Example;

    [VBOptions]
    AxextDelay=30
    

DISCLAIMER:

Some content on Community Tips & Information pages is not officially supported by Micro Focus. Please refer to our Terms of Use for more detail.
Top Contributors
Version history
Revision #:
1 of 1
Last update:
‎2013-02-15 19:22
Updated by:
 
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.