This article has been archived. It is offered "as is" and will no longer be updated.
Microsoft has released Microsoft Office XP Developer Service Pack 1 (SP-1). This article describes the problems that are fixed for Office XP Developer SP-1.
How to Download and Install Microsoft Office XP Developer SP-1
To obtain Microsoft Office XP Developer SP-1, see the following Microsoft Knowledge Base article:
313166 HOW TO: OFFXPDEV: How to Obtain and Install Office XP Developer Service Pack 1 (SP-1)
How to Determine Whether SP-1 Is Installed
To determine whether SP-1 is installed, see the following Microsoft Knowledge Base article:
313172 OFFXPDEV: How to Determine If Office XP Developer Service Pack 1 (SP-1) Is Installed on Your Computer
Issues Fixed by SP-1
Office XP Developer SP-1 fixes the following problems.
When you use Find in the Code Librarian Viewer, you may not receive the results that you would expect. For example, if you search for "A B" (including a space between the characters) the space is ignored.
When you use the File Save Copy As command, it appears that you can save a Web Part as a different type, for example, save a .vbs Web Part as a .xml Web Part. This does not create a new file type for the Web Part. The available file types have been modified to reflect this behavior.
You cannot remove a sub-dashboard from a dashboard without deleting the sub-dashboard.
When you try to use Office Developer XP to edit a Web Part that was created in an Office application and that application is still open, you received an error message.
A dashboard does not display the sub-dashboards, as you would expect. You may experience this behavior if the name of the dashboard uses characters from the double-byte character set.
When you enter a numeric value other than one (1) or zero (0) into the AutoUpdate property of a dashboard, the property reverts to null. Also, if the dashboard losses focus, the AutoUpdate property is no longer available when it regains focus.
When you try to open the project after you have saved it to a different server and closed it, you receive the following error message:
The project file format cannot be read. The project will not be opened.
Then the project is not opened.
On a computer that is running Microsoft Windows 98, you may receive an error message on a blue screen after you add a Web Part, and then try to save the dashboard.
A dashboard may unexpectedly close when you try to add another dashboard onto the first one. This can occur when the name of the dashboard that you are adding has characters from the double-byte character set (DBCS).
When you use the Add Existing Item dialog box in a dashboard project, you cannot select multiple items at one time.
The Web Parts that are included with Office XP Developer are not final versions and are not intended for use in production dashboards. You can obtain final versions of the Web Parts from the Microsoft Web Part Gallery link in the Content page of a deployed dashboard. The final versions are included with Office XP Developer SP-1.
Add Existing Item is not available on the Project menu on a portal or a sub-dashboard within a portal.
Documentation and Help
When you search for Help topics, you may not receive the results that you would expect or no topics are returned in the Japanese version of the Microsoft Office XP Developer Online Documentation.
When you try to start Help, if you installed Microsoft Visual Studio 6.0 after you installed Office XP Developer Edition, you receive the following error message:
Unable to display Help: A required component is missing. Please reinstall.
When you install Microsoft Office XP Developer after you install the .NET Framework software developer's kit (SDK), Visual Studio .NET, or any edition of the MSDN Library designed for Visual Studio .NET, the Office Developer Help documentation is not available.For additional information, click the article number below to view the article in the Microsoft Knowledge Base:
313496 PRB: Office Developer Help Documentation Is Not Available When You Install Microsoft Office XP Developer
The Resume <label> line is left out if the code inserted by the VBA Error Handler. This results in two exit points from the procedure.
Microsoft Development Environment
The Solution Explorer does not display an icon next to the title of the solution.
When you click Navigate Backwards in the Microsoft Development Environment, the Microsoft Development Environment will unexpectedly quit or stop responding.
When you right-click the Script node in the Document Outline that is bound to an Exchange or SQL Server Process Definition Code View, the Microsoft Development Environment may stop responding.
When you try to paste a Unicode character into a property window of the Exchange Workflow Designer, Workflow Designer for SQL Server, or a Digital Dashboard, the character is not what you would expected. For example, you see a question mark (?) instead of the correct character.
If you remove Microsoft Visual Studio .NET, the file association for solution files (*.snl) is broken.
Multi-Code Import and Export
On a computer that is running Microsoft Windows 98, when you try to export a module that uses the Multi-Code Export add-in, the computer stops responding.
A memory leak that may occur when building packages was corrected.
When you install a Microsoft Access 2002 run-time package on a Microsoft Windows NT 4.0-based computer, the system update part of the Setup is installed, but you are not prompted to restart the computer. The remaining part of the package Setup fails silently, and therefore the Setup is never completed.
A package that you created by using Microsoft Office XP Developer cannot beinstalled correctly on a computer that is running Microsoft Windows 98. The user receives no error message. The user receives a notification that states that the files are being copied, but then nothing. The package may prompt you to restart the computer. But after the operating system is running again, Setup does not continue.
When you try to install a run-time application that was created with Microsoft Office XP Developer and distributed on CD to a computer that is running Microsoft Windows 98 or Microsoft Windows Millennium Edition (Me), you receive the following error message:
Path/File access error
An unexpected setup error has occurred!
In the error message box, there are two buttons: Retry and Cancel. When you click Retry, you see the same error message. When you click Cancel, you see additional error messages that indicate that the installation has failed.
When you install an Access 2002 run-time application that includes the Microsoft SQL Server 2000 Desktop Engine from a CD or from a read-only folder, you receive the following error:
Path/File access error
An unexpected setup error has occurred!
When you install a package that includes the SQL Server 2000 Desktop Engine, you may not be able to see the full path to the Database Server on a button caption during the installation.
When you package a database that was converted from Access 2000 to Access 2002, the file Owc10.dll (which is not necessary) is automatically added to the package.
When you build a package, the main window of the Packaging Wizard disappears behind the Visual Basic Editor window. It remains there until you click Packaging Wizard on the taskbar to bring it back to the front.
You successfully create one package. You then try to create an additional package of the same database in a different language. But you do not first close and then reopen Access. The result is that the Packaging Wizard does not include the run-time files in the second package.
When you save an Exchange Workflow file (*.wef) in the same folder as another *.wef file with the same name, the original file is overwritten without warning.
There is an error in the modhtmtosql.bat file that causes some .sql files to be converted into English instead of to the correct language.
While you are creating a workflow project in a public folder on the Exchange Server, when you add a transition from the Start shape to a State shape, the system becomes unresponsive.
When you select and try to add multiple workflow processes in the Add Existing Item dialog box, you are prompted for each item even though you click Apply To All.
Workflow Process Definitions that are created in Microsoft Office 2000 Developer that include expiry intervals, will display the expire interval as a decimal of days. For example, if you set an Expiry Interval of 15 minutes in the Office 2000 Developer version, after migration to Microsoft Office XP Developer, the Expiry Interval is displayed as 0.01041666667 days.
The OnExpiry event does not fire after you upgrade Workflow Process Definitions from Office 2000 Developer to Office XP Developer. The event procedure is not accurately migrated.
To fix this problem, after the Workflow has been migrated, update the syntax from OnExpiry() to OnExpire(). For example, change OnExpiry
Sub Expire1_OnExpiry() Workflowsession.addauditentry "Active Expired"End Sub
Sub Expire1_OnExpire() Workflowsession.addauditentry "Active Expired"End Sub
If you copy a Workflow Process Definition file by using the Copy command, and you then paste it into a different public folder where a Workflow Process Definition file of the same name exists, you will be prompted to replace it. However, if you paste the file back into the folder from where you copied it, rather than being overwritten when you click Yes to replace the file, it will create a second copy of the file. For example, you will have a Process1.wfd and a Process1(2).wfd file.
The Verify Script Tool does not remove a Script Error from the Task List after the error has been fixed. The Task List is only refreshed after another error has been added.
When you try to view a code window immediately after you add an existing workflow to a solution, you receive the following error message:
To open a code window without receiving the error message, you must first close and then reopen the Workflow Solution.
When you try to open a Workflow Designer for SQL Server project after you change the RowPermissions property and close the project, you receive the following error message even if it is not locked by another user:
The project database is locked by another user.
The Workflow Manager for SQL Server may unexpectedly quit if you are working with table names that are longer than 57 characters.
You may not be able to open a workflow project if you recently closed the project and you are using Microsoft SQL Server 2000 Personal Edition.
When you add an existing Workflow to the current Workflow project, all files are displayed instead of just *.wfs files. Additionally, you can select a different file type and select to add the file to the Workflow project.
When you try to use the Solution Explorer to create a blank process definition, you receive an message that the process definition was created in an earlier version.
If script updates the modStateID value during an onCreate event, the Workflow Manager for SQL Server will stop responding.
When you try to view the properties of a User Account, the Workflow Manager for SQL Server may generate error messages and then quit.
Updates have been made to the Default.htm and ClientHelp.htm pages for the Workflow Designer for SQL Server.
The New Microsoft SQL Server Login dialog box displays characters that are not valid in the User Names box when you are using the SQL Server Workflow Template Instantiation Wizard.
When you try to save a template to file by using the Save to File option from a workflow client computer, you receive the following error message:
Error trying to create template. DCOM server modTBAD failed to successfully complete the task.
Additionally, the template is not saved to file. It remains in the modSystem database on the workflow server.
When you try to add a lookup table to a Workflow Designer for SQL Server project by using the Lookup Table dialog box drop-down list, the drop-down list does not respond, and you cannot select a lookup table from the list.
crashes freezes hang run time runtime DBCS corrected updated fixlist fix list