Microsoft KB Archive/241715

= MOD2000: Access Workflow Designer Readme Contents =

Article ID: 241715

Article Last Modified on 6/24/2004

-

APPLIES TO


 * Microsoft Office 2000 Developer Edition
 * Microsoft Access 2000 Standard Edition

-



This article was previously published under Q241715



Advanced: Requires expert coding, interoperability, and multiuser skills.



SUMMARY
The Access Workflow Designer has two readme files: one for the server components, and one for the developer components. You can view these files after you install the relevant set of components, or you can view these files directly from the Access Workflow Designer media.



MORE INFORMATION
If you do not install the server components or the developer components, the readme files are located in the WkflowDS\Help folder as modServerReadme.htm (server components readme) or modClientReadme.htm (developer components).

After you install the server components, the server components readme file resides in the folder where the server components are installed (by default, C:\Program Files\Microsoft Office Developer) as modServerReadme.htm.

After you install the developer components, the developer components readme file resides in the folder where the developer components are installed (by default, C:\Program Files\Microsoft Office Developer) as modClientReadme.htm.

Access Workflow Designer Server Installation Notes, modServerReadme.htm

- Software Requirements - End-User Client Setup - Access Workflow Designer Tools Setup - What is Microsoft Office Developer Access Workflow Designer? - Release Notes and Known Issues

Server Issues =============   - Internet Explorer settings on the server may cause Microsoft Office Developer to not work correctly. - Issues with reinstalling Access Workflow Designer on the server when subscriptions still exist. - Potential problems when using the same computer as the server and the client. - Terminology issues in the online documentation. - Do not use Japanese characters in your Web site name if you have an      English server.

End-User Issues ===============   - Errors can occur during synchronization of offline subscriptions. - If the server is not available, users will receive a script run-time error when trying to resolve conflicts. - Issues with removing local databases when removing a subscription. - When filtering data on the client, locale settings will impact filter results. - Potential issues with two-digit years because of SQL Server and ADO defaults.

Database Issues ===============   - SQL Server 7.0 is required on the server for this release.

Naming Issues =============

Team Solutions Manager Issues =============================   - Always synchronize the user directory when adding or removing database users. - Issues with synchronizing the User Directory. - The Find Mailbox dialog box only works when ADSI OLEDB is installed. Access Workflow Designer Tools Installation Notes, modClientReadme.htm

- Software Requirements - End-User Client Setup - Access Workflow Designer Server Setup - What is Microsoft Office Developer Access Workflow Designer? - Release Notes and Known Issues

General Issues ============== - There is no Undo feature in this version of the Access Workflow Designer. - Multiple developers should not access the same database at the same time using the Access Workflow Designer tools.

Naming Issues ============= - SQL Server permissions errors may occur when installing Access Workflow Designer Tools on a Windows 95/98 computer. - Issues with the Microsoft Office Developer Workflow Toolbar Control. - Terminology issues in the online documentation. - Do not use Japanese characters in your solution name if you have an    English server.

Database Issues =============== - Do not rename user tables in the solution database. - New tables added after defining main user tables are not recognized automatically by the Access Workflow Designer. - When creating user views for the user interface, make sure to use base views rather than user tables to ensure row permissions are enforced. - Making any permissions changes or row changes to the Issue Tracking solution requires you to update the IssuesBaseView manually. - Row-level permissions on main tables prevent making schema changes. - Permissions issues may result when changing the login defined as    database owner (DBO) before registering a database. - Potential date issues for the end user.

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

Offline Replication Issues ========================== - Offline publication names cannot contain spaces before or after the name. - Adding main tables that are included in publications requires the re-creation of the publication. - Offline replication will fail if the replicated table contains timestamps. - The SQL Server Agent must be running to create publications. - Offline subscriptions cannot be created on server.

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.

Additional query words: access workflow designer readme contents server components developer modServerReadme modClientReadme

Keywords: kbinfo kbworkflowdesigner KB241715

-

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

© Microsoft Corporation. All rights reserved.