Microsoft KB Archive/285157

= MOD2000: Microsoft Office 2000 Developer Edition Service Pack 2 Readme File Contents =

Article ID: 285157

Article Last Modified on 1/20/2006

-

APPLIES TO


 * Microsoft Office 2000 Developer Edition

-



This article was previously published under Q285157



SUMMARY
The More Information section of this article contains a copy of the information in the ReadmeOD.htm file included in the Microsoft Office 2000 Developer Edition Service Pack 2 (SP-2).



Contents

 * Microsoft Office 2000 Developer Installation Notes
 * Installing Office Developer Service Pack 2
 * Knowledge Base and Microsoft Office Developer
 * Modified Files in Microsoft Office 2000 Developer SP-2
 * Release Notes and Known Issues
 * Known Issues: Server and End-User Components for Access Workflow Designer for SQL Server
 * Known Issues: Developer Tools Components for Access Workflow Designer for SQL Server

Installing Office Developer Service Pack 2
Office Developer SP2 contains a number of installation options. Select the appropriate SP2 files to install. Each file is a self-extracting executable that installs the latest version of the product, except for the patches, which install only the updated files.

SQL Server Workflow Setup - contains the full setup for the server components for the Access Workflow Designer for SQL Server

SQL Server Workflow Client Setup - contains the full setup for the developer tools for the Access Workflow Designer for SQL Server

SQL Server Workflow Silent Client Setup - contains the full setup for the client runtime for the Access Workflow Designer for SQL Server

MODSP2 Patch - contains updates that can be applied to any existing Office Developer installation; includes SR1 updates for both workflow and productivity tools

Installation Notes:

To locate the product identification (PID) number in the Help About dialog box for product support for this version of Office Developer, you must have the original product installed.

To upgrade an existing SQL Server 7.0 installation that is enabled for workflow, first upgrade your server to SQL Server 2000 and then upgrade the Office Developer workflow components on the server using the MODSP2 Patch.

To install the Office Developer workflow components on a server with SQL Server 2000, you must use the SQL Server Workflow Setup executable. The setup program from the original Office Developer 9, Version 1.5 release will not work with SQL Server 2000.

Knowledge Base and Microsoft Office Developer
The Microsoft Knowledge Base, available on the Microsoft Web site, contains technical articles on Microsoft products, including Office 2000 Developer. The articles contain Office Developer samples, tips, and additional data.

The Knowledge Base contains primarily articles in English, but there are many localized articles as well. If you search under a localized name and do not find anything, use the English name of the component in the search.

Modified Files in Microsoft Office 2000 Developer SP-2
Service Pack 2 contains updates that make it possible for the Access Workflow Designer for SQL Server to work with Microsoft SQL Server 2000.

The following files have been modified in this release of Microsoft Office 2000 Developer.

modtbad.exe

modappwiz.exe

userlist.exe

modrepllogxp.dll

modreplsetup.dll

modreplsink.dll

modreplxp.dll

modresolver.dll

modwc.dll

modwc.cab

Release Notes and Known Issues
The known issues for this version of Office 2000 Developer are divided into two main sections:
 * Known Issues: Server and End-User Components for Access Workflow Designer for SQL Server
 * Known Issues: Developer Tools Components for Access Workflow Designer for SQL Server

For additional assistance with this product, consult the Product Support sections of the Office 2000 Developer Web site at http://msdn.microsoft.com/office.

Known Issues: Server and End-User Components for Access Workflow Designer for SQL Server
The following feature areas have issues that are known in this version of Access Workflow Designer:
 * Server Issues
 * End-User Issues
 * Database Issues
 * Team Solutions Manager Issues

For solution development and development tools issues, see the Access Workflow Designer Tools Readme (modClientReadme.htm) file and the Troubleshooting section in the Access Workflow Designer Developer's Guide (modDevGuide.chm).

For issues concerning other Office Developer components, see the Microsoft Office Developer Readme (ReadmeOD.htm) file at the root of the Microsoft Office Developer CD-ROM.

For additional assistance with this product, consult the Product Support sections of the Office 2000 Developer Web site at http://msdn.microsoft.com/office.

Server Issues
Internet Explorer settings on the server might cause Microsoft Office Developer to not work correctly.

During the creation of solutions on the server, Microsoft Office Developer uses a version of Microsoft Internet Explorer that does not have a user interface. This version is used to get and to set data access page connection properties. If the version of Internet Explorer installed on the server is configured to &quot;Use the automatic configuration script,&quot; and the configuration script sends prompts to the user (for example, to warn the user about downloading controls), the server will appear to hang, and creation of the solution will not work.

To work around this issue, do one of the following:
 * Turn off the &quot;Use automatic configuration script&quot; option in Internet Explorer 5.
 * On the server, open Internet Explorer.
 * From the Tools menu, select Internet Options.
 * On the Connections tab, click LAN Settings.
 * Clear the Use automatic configuration script option, and click OK.
 * Launch Internet Explorer 5 manually on the server, and dismiss all prompts and dialog boxes before performing the action that hangs the Access Workflow Designer (for example, creating a new solution from a template).

If the problem continues after performing these solutions, try restarting the server. Issues with reinstalling Access Workflow Designer on the server when subscriptions still exist.

To reinstall Access Workflow Designer on the server, delete all Access Workflow Designer publications from the server and subscriptions from the client. If you try to reinstall the server components while client subscriptions still exist, you will receive errors on the client. Remove all offline subscriptions to team solutions as part of the uninstall process on the client to avoid these errors.

Potential problems when using the same computer as the server and the client.

If you are using the same computer as both the server and the client and you receive an &quot;object not found&quot; error message when deploying a solution, this is most likely because of an issue with the proxy server. If you must use a proxy server, try the following to resolve the issue:
 * 1) Right-click the Internet Explorer icon on the desktop, and select Properties from the shortcut menu.
 * 2) In the Internet Explorer Properties dialog box, select the Connections tab.
 * 3) Click the LAN Settings button to open the Local Area Network (LAN) Settings dialog box.
 * 4) In the Proxy Server section on the dialog box, select the Bypass proxy server for local addresses option.

Authentication Problems using Pre-Release Versions of Windows 2000 as a Domain Controller.

Note: These issues apply to the pre-release versions of Microsoft Windows 2000 only. To resolve these issues, install the released version of Windows 2000.

When you connect a remote Windows-based client to a Microsoft Windows NT 4.0 Remote Access Server (RAS) or Routing and Remote Access Server (RRAS) that is a member of a Windows 2000 domain, authentication might not succeed if you log on with a Windows 2000 domain account.

Additionally, authentication might not succeed when you connect to a remote access server running Windows 2000 that is a member of a Windows NT 4.0 domain accessing user account properties for a user account in a trusted Windows 2000 domain.

If you log on with a local account to Windows NT 4.0 RAS/RRAS or Windows 2000, you might connect successfully.

To enable a Windows 2000 domain controller to make it possible for a RAS or RRAS server running Windows NT 4.0 Service Pack 4 or later or a remote access server running Windows 2000 in a trusted Windows NT 4.0 domain to access user account properties of a remote Windows 2000 domain controller, select the option for &quot;Permissions compatible with pre-Windows 2000 servers&quot; during the domain controller promotion process (DCPromo). Or, type:

net localgroup &quot;Pre-Windows 2000 Compatible Access&quot; everyone /add

at a Windows 2000 command prompt on the domain controller computer, and then restart the domain controller computer.

If your Windows 2000 Active Directory was upgraded from a pre-release version prior to Release Candidate 2 (RC2), the new built-in group &quot;Pre-Windows 2000 Compatible Access&quot; requires a schema and security update. If you installed a new Active Directory with RC2 or later, you do not require and should not apply the following fix.

A supported fix that corrects this problem is now available from Microsoft. Contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please visit the following address on the World Wide Web:

http://support.microsoft.com/contactus/?ws=support

Please refer to your Beta documentation for information on how to obtain support and fixes for Windows 2000 RC2.

Terminology issues in the online documentation.

In the online documentation, references to &quot;db_user&quot; should refer to &quot;database user,&quot; and references to &quot;db_creator&quot; should refer to the &quot;dbcreator&quot; or the &quot;Database Creators&quot; fixed server role.

Do not use Japanese characters in your Web site name if you have an English server.

If you are using an English server, do not use Japanese characters when creating the name of your team solution Web site. Microsoft FrontPage 2000 cannot create the proper Web folder with the Japanese characters. This causes Access Workflow Designer to fail when creating a new solution.

End-User Issues
As a solution administrator, you might want to notify users of the following issues: Errors can occur during synchronization of offline subscriptions.

If solution users receive messages during synchronization indicating that errors occurred while downloading a URL, problems might exist in the user's offline content. To correct the problem, the user should follow these steps:
 * 1) Right-click the Internet Explorer icon on the desktop, and select Properties from the shortcut menu.
 * 2) On the General tab, in the Temporary Internet Files section, click Delete Files.
 * 3) In the confirmation box, select Delete all offline content.
 * 4) Click OK.
 * 5) Re-create the subscription to the solution.

If the server is not available, users will receive a script run-time error when trying to resolve conflicts.

If the user synchronizes the offline database, chooses not to review conflicts at that time, and then tries to view conflicts while the server is unavailable, the user will receive an Internet Explorer Script Error. To view and resolve conflicts, the user must wait until the server is available.

Issues with removing local databases when removing a subscription.

Whenever you remove a subscription, the local database is not deleted at the same time, because it is in use. You can delete the offline database manually after removing the subscription.

When filtering data on the client, locale settings will impact filter results.

If the solution user has a different locale setting than the settings used by SQL Server, there are potential problems when filtering solution data. For example, if the server interprets September 16, 1999 as 9/16/99 and the client interprets September 16, 1999 as 16/9/99, when the user enters 16/9 as the filter criteria, the filter engine will attempt to read the entry in the month/day format and will find no matching records. To avoid this problem when filtering, be sure to enter data using the format of the SQL Server locale. Potential issues with two-digit years because of SQL Server and ADO defaults.

By default, the cutoff years used by SQL Server and ADO to interpret two-digit dates are different. This can cause different areas of your team solution to translate the same two-digit year into dates in different centuries. To guarantee consistency in date behavior, it is recommended you set the SQL Server two-digit year cutoff to be 2030, or use four-digit years in your data.

Potential end-user problems with adding new records using the Record Navigation control.

If a data access page contains both the Record Navigation control and the Workflow Toolbar control, users might encounter problems when entering new records. The New Record button on the Record Navigation control might not work properly. In some cases, the fields on the data access page might be locked, so users cannot enter new information.

To avoid this problem, or if New Record button on the Record Navigation control does lock the fields, users should use the New Record button on the Workflow Toolbar instead.

Database Issues
SQL Server 7.0 or later is required on the server for this release.

The server must contain SQL Server 7.0 with Service Pack 2 or SQL Server 2000. Microsoft Data Engine (MSDE) is not supported as the data store on the server at this time.

Offline features will not work if SQL Server 2000 is in Windows Authentication Mode.

SQL Server 2000 must be installed using &quot;Mixed Mode&quot; security in order for Access Workflow Designer offline features to function. By default, SQL Server 2000 installs using Windows Authentication Mode. To take advantage of offline workflow features, you will need to reinstall SQL Server 2000 using Mixed Mode.

Naming Issues  Any template or publication containing the following characters cannot be deployed successfully:

* [ ] \ | / < > : &quot; ? %

Rename any template or publication that fails to work correctly. Do not create solutions whose names differ only by additional words at the end. Avoid using solution and database names that have the same starting characters followed by a space and a delineating word, such as &quot;IssueTracking&quot; and &quot;IssueTracking Test.&quot; This might cause problems when subscribing to and synchronizing team solution publications. To avoid this issue, do not use spaces, or ensure the characters before the space are unique.

Team Solutions Manager Issues
Always synchronize the user directory when adding or removing database users.

Unless you manually synchronize the user directory after adding or removing database users, the user directory will not be updated until the next scheduled automatic synchronization. Therefore, new users might not have sufficient permissions to access items in the database.

Issues with synchronizing the User Directory.

To use Windows NT or Windows 2000 domain and Microsoft Exchange Server synchronization with the user directory, SQL Server must be logged in as a Windows NT domain account. If you change the MSSQLServer Service to log in as the System Account instead, synchronization will not be successful.

If you receive errors during synchronization, this might be because your database contains standard SQL Server logins instead of Windows NT user logins. Using a standard SQL Server login might result in an error saying &quot;Exceptions occurred while invoking method SynchronizeUserList Error(80004005) in Microsoft Cursor Engine.&quot; If you receive this error during synchronization, remove any standard, non-Windows NT user logins from your database and try again.

The Find Mailbox dialog box only works when ADSI OLEDB is installed.

In the Team Solutions Manager, you can add detailed information about users manually by selecting a user and clicking Edit User on the User Information tab. If you attempt to open the Find Mailbox dialog box from the User Details window, you might get the following error: &quot;Error: ADO could not find the specified provider.&quot; For the Find Mailbox dialog box to work correctly, you must install ADSI OLEDB.

Known Issues: Developer Tools Components for Access Workflow Designer for SQL Server
The following feature areas have issues that are known in this version of Access Workflow Designer:
 * General Access Workflow Designer Issues
 * Database Issues
 * Workflow Issues
 * Offline Replication Issues
 * Security and Permissions Issues

For server and solution administration, as well as end-user issues, see the Access Workflow Designer Server Readme (modServerReadme.htm) file and the Troubleshooting section in the Access Workflow Designer Developer's Guide (modDevGuide.chm).

For issues concerning other Microsoft Office Developer components, see the Microsoft Office Developer Readme (ReadmeOD.htm) file at the root of the Microsoft Office Developer CD-ROM.

For additional assistance with this product, consult the Product Support sections of the Office 2000 Developer Web site at

http://msdn.microsoft.com/office.

General Access Workflow Designer Issues
There is no Undo feature in this version of the Access Workflow Designer.

When working with the Access Workflow Designer, your changes are saved to the solution as you make them, and there is currently no way to undo an action. To remove workflow features from your solution, you must remove all components from the database manually.

Multiple developers should not access the same database at the same time using the Access Workflow Designer tools.

The Access Workflow Designer is designed to make it possible for only one developer to work on a solution database at a time. Unpredictable behavior might result if more than one developer opens and modifies a single database at the same time. To avoid potential problems with your database, permit only one person to access the database at a time.

Naming Issues  Any template or publication containing the following characters cannot be deployed successfully:

* [ ] \ | / < > : &quot; ? %

Rename any template or publication that fails to work correctly. Do not create solutions whose names differ only by additional words at the end. Avoid using solution and database names that have the same starting characters followed by a space and a delineating word, such as &quot;IssueTracking&quot; and &quot;IssueTracking Test.&quot; This might cause problems when subscribing to and synchronizing team solution publications. To avoid this issue, do not use spaces, or ensure the characters before the space are unique.

Issues with the Microsoft Office Developer Workflow Toolbar Control.
 * Do not use more than one toolbar control per data access page. In addition, when placing the control on your page, make sure it is not inserted into a band in a data access page.
 * If a data access page contains both the Record Navigation control and the Workflow Toolbar control, users might encounter problems when entering new records. The New Record button on the Record Navigation control might not work properly. In some cases, the fields on the data access page might be locked, so users cannot enter new information.

To avoid this problem, or if the Record Navigation control New Record button does lock the fields, users should use the New Record button on the Workflow Toolbar instead.
 * The Workflow Toolbar UseKeyUpdateCriteria property must be set to True if the row-level permissions feature is being used. When UseKeyUpdateCriteria is set to True, the UpdateCriteria property for the data source's recordset is set to adCriteriaKey.

UpdateCriteria controls how collisions between concurrent updates are detected and handled during the update process. With row-level permissions, users only have select permissions on the key column in the table underlying the row-permissions view. The adCriteriaKey setting is required to make it possible for updates to succeed with this permissions setting, but it changes the default update concurrency behavior of data access pages. More information about UpdateCriteria is available in the MSDN Library.
 * The Workflow Toolbar does not respond dynamically to changes in the page or the data source. If the toolbar displays an error message in design mode (such as &quot;UniqueTable property not set&quot;), you might be required to close and to reopen the data access page designer after correcting the problem for the toolbar to update itself.
 * If you create an action name that contains a single quotation mark ('), that action will never be available in the toolbar. To avoid this problem, do not use single quotation marks in action names.

Terminology issues in the online documentation.

In the online documentation, references to &quot;db_user&quot; should refer to &quot;database user,&quot; and references to &quot;db_creator&quot; should refer to the &quot;dbcreator&quot; or the &quot;Database Creators&quot; fixed server role.

Do not use Japanese characters in your solution name if you have an English server.

If you are using an English server, do not use Japanese characters when creating the name of your team solution. Microsoft FrontPage 2000 cannot create the proper Web folder with the Japanese characters. This causes Access Workflow Designer to fail when creating a new solution.

Database Issues
Do not rename user tables in the solution database.

The Access Workflow Designer does not support the renaming of main, detail, or lookup user tables after they have been added to the database. If you must rename a table, delete the table from the Access Workflow Designer, rename it, and then add it back to the Access Workflow Designer.

New tables added after defining main user tables are not recognized automatically by the Access Workflow Designer.

When a table has been defined as a main, detail, or lookup table in the Access Workflow Designer, changes you make to the foreign-key constraints that relate it to other tables are not detected automatically by the Access Workflow Designer.

If you change the foreign-key constraint that relates a detail or lookup table to its parent table, you must open the table properties in Access Workflow Designer and click the Find Foreign-Key button to update the relationship.

If you add a new foreign-key constraint, you can add the related table to a parent main or detail table manually by selecting Insert from the Edit menu and choosing Detail Table or Lookup Table.

If you delete a foreign-key constraint relating a detail or lookup table to its parent table, then you should remove the related table from the Access Workflow Designer by selecting the node for the table in the Object List and choosing Remove from the Edit menu.

When creating user views for the user interface, make sure to use base views rather than user tables to ensure row permissions are enforced.

Row-level permissions are assigned by the user entering the issues into the solution. When developing a solution, be sure to design your tables to ensure row-level permissions can be enforced by the user. To do this, follow these steps:
 * 1) In the Access Workflow Designer, select a main table to which you want to add row-level permissions, and then select the General tab in the right pane. The name of the base view for the table is displayed on this tab. The name is in the format View, for example, IssuesView. Design the user interface to connect to and perform actions against the base view of this main table instead of the table itself, for example, IssuesBaseView.
 * 2) When you add core services to an existing database, column privileges on the tables you modify will change if the table has a primary key. In particular, select permissions are granted to Public on the primary-key column, and insert and delete permissions are granted to Public on the table. Those changes make the table updateable from data access pages.

Making any permissions changes or row changes to the Issue Tracking solution requires you to update the IssuesBaseView manually.

If you make any changes to column- or row-level permissions to the Issue Tracking solution, you must update the IssuesBaseView manually with those changes. The IssuesBaseView is not updated automatically with changes you make to the Issues or IssuesView tables.

Row-level permissions on main tables prevent making schema changes.

If you identify a database table as a main table and then define row-level permissions for that table, you might receive an error if you later attempt to make schema changes to that main table. To make schema changes to tables used by Access Workflow Designer, you must remove the table from the Access Workflow Designer, make the schema changes, and then add the table again.

Potential date issues for the end user.

When designing your solution, it is recommended you attempt to provide a user interface that avoids the following issues:
 * If the solution user has a different locale setting than the settings used by SQL Server, there are potential problems when filtering solution data. For example, if the server interprets September 16, 1999 as 9/16/99 and the client interprets September 16, 1999 as 16/9/99, when the user enters 16/9 as the filter criteria, the filter engine will attempt to read the entry in the month/day format and will find no matching records. To avoid this problem, when filtering be sure to enter data using the format of the SQL Server locale.
 * By default, the cutoff years used by SQL Server and ADO to interpret two-digit dates are different. This can cause different areas of your team solution to translate the same two-digit year into dates in different centuries. To guarantee consistency in date behavior, it is recommended you set the SQL Server two-digit year cutoff to be 2030, or use four-digit years in your data.

Workflow Issues
Workflow permissions for workflow actions might require the SQL Server database owner logins to be changed.

If you set workflow permissions on a workflow action, the database owner (dbo) of your database might not have permissions to perform the action any longer, even if permissions are granted to Public and the dbo was able to perform the transition earlier.

To work around this, make sure the SQL login or Microsoft Windows NT or Microsoft Windows 2000 account assigned to the dbo user also has access to the database through another database user (such as modAppOwners), and verify that this user is assigned to the role that has workflow permissions. After you make this change, be sure to synchronize the user directory on the server using the Team Solutions Manager to update the modUserRoles table in the database.

Offline Replication Issues
Offline publication names cannot contain spaces before or after the name.

When creating offline publications, the publication name cannot contain any spaces before or after the name, because the creation of the publication will fail. Make sure you remove any leading or trailing spaces when entering the publication name.

Adding main tables that are included in publications requires the re-creation of the publication.

When you add a main table to your solution after publications exist, the main table and its dependencies might not be included correctly in the publication. If the table was included in an existing publication as a dependency before it was identified as a main table, the table appears selected in the list of main tables to replicate for the publication. However, the table's related objects, such as the base view, workflow table, detail tables, and lookup tables, might not be included in the publication. As a result, replication joins for filtering detail tables based on the main table are not defined.

To add the main table's related objects to the publication, in the Access Workflow Designer, select the publication in the Object List to display the Offline Publications pane. On the Tables tab, clear and then select the table in the list of main tables. Then, re-create the publication.

Offline replication will fail if the replicated table contains timestamps.

Access Workflow Designer does not support tables with timestamps in offline publications. The publication might be created but will not work properly. To resolve this issue, remove the table from the publication or the timestamp from the table, and re-create the publication.

The SQL Server Agent must be running to create publications.

A publication cannot be created if the SQL Server Agent is not running when you attempt to create a publication. If you receive errors while attempting to create a publication, verify that the SQL Server Agent is running. If it is not, start the SQL Server Agent, and try to create the publication again.

Offline subscriptions cannot be created on the publication server.

When the server contains a copy of the publication database, if you attempt to create an offline subscription on that server, error messages indicating a database with the same name already exists will occur. Do not create offline subscriptions on the same server that contains the publication.

Replication errors might occur after renaming SQL views.

If you rename a SQL view, its associated CREATE text in the view definition is not updated with the new name. Consequently, during replication the initial snapshot creation fails, because it uses the new view name, while SQL Server uses the old name. You must change this name manually in the view definition.

To change the view name in the CREATE text manually:
 * 1) In SQL Server Enterprise Manager, navigate to the view.
 * 2) Right-click the view, and select Properties.
 * 3) Change the text after &quot;CREATE VIEW&quot; (usually the first line of the view) to match the new name.

Security and Permissions Issues
To create new SQL logins and database users with MSDE, use the version of MSDE provided with Office 2000 Premium or SQL Server.

To create new SQL logins and database users when using Microsoft Data Engine (MSDE) as the data source, you must use the version of MSDE included in Office 2000 Premium or SQL Server 7.0. Do not install the redistributable version of MSDE provided in Office 2000 Developer. To manage logins, in the Access Workflow Designer, from the Tools menu, select Database Security.

Keywords: kbinfo kbreadme KB285157

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.