MOD2000: Visual Basic for Applications Code in a Run-Time Application Does Not Run on Terminal Server (288767)


The information in this article applies to:

  • Microsoft Office 2000 Developer
This article was previously published under Q288767

SYMPTOMS

If you install a Microsoft Access run-time application on a Microsoft Windows NT or a Windows 2000 Terminal Server, the Microsoft Visual Basic for Applications (VBA) code in the application does not run.

CAUSE

The Access run-time application was not installed correctly; that is, the Access run-time application was installed through a Terminal Server client session rather than at the Terminal Server console.

RESOLUTION

To resolve this issue, at the Terminal Server console, log in as an Administrator, and then follow these steps:
  1. Uninstall the Access run-time component.
  2. Install the Access run-time component by re-running the installation program using the Termsrvr_Art.mst transform.
  3. After the reboot, test the application. The code should now run.

MORE INFORMATION

To obtain the run-time transform, click the following link:

http://www.microsoft.com/office/ork/2000/download/Termsrvr_ART.mst

Steps to Reproduce the Behavior

  1. Create an Access application that has a command button on a form that uses Visual Basic for Applications (VBA) code to open another form.
  2. Using the Package and Deployment Wizard, create redistributable Setup files for this application.
  3. While logged on to the Terminal Server as an Administrator, from a client computer, install the Access run-time application to the Terminal Server using the Termsrvr_ART.mst transform.
  4. Once Setup has finished, start the run-time application, and then click the button to open the form. Note that nothing happens.
Modification Type:MajorLast Reviewed:4/17/2006
Keywords:kbprb KB288767
©2004 Microsoft Corporation. All rights reserved.