ACC2000: Cannot Install Microsoft Script Editor "On First Use" on Terminal Server

• Microsoft Access 2000

SYMPTOMS

When you run Access 2000 on Microsoft Terminal Server, the Microsoft Script Editor does not start when you click the Microsoft Script Editor command on the Tools menu.

CAUSE

Although the Microsoft Script Editor command does appear on the Tools menu, the Microsoft Script Editor cannot be installed on Terminal Server. The Microsoft Script Editor is not compatible with Terminal Server.

RESOLUTION

If you want to use the Script Editor, do not run Access 2000 on Terminal Server. Instead, run Access 2000 on a computer on which Windows 95 or later or Windows NT is installed.

STATUS

Microsoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article.

MORE INFORMATION

Steps to Reproduce Behavior

1. Perform a default setup on Terminal Server of one of the following products:



• Microsoft Office 2000 Professional
• Microsoft Office 2000 Premium
• Microsoft Access 2000


2. Log on to a Terminal Server client computer, and run Access 2000.



3. In the Database window, click Pages under Objects, and then click New.



4. On the Tools menu, point to Macro, and then click Microsoft Script Editor.

REFERENCES

For information about installing Office on Terminal Server, check the Microsoft Office 2000 Resource Kit. You can also get more information from the Microsoft Office 2000 Resource Kit Web page at:

http://www.microsoft.com/office/ork/2000/

Additional query words: pra prb hangs transform custom unavailable mde development environment install on first use

Keywords : kbdta
Version : WINDOWS:2000
Platform : WINDOWS
Issue type : kbbug