Share via

Troubleshooting: Security and Permissions Issues

  • Article

This content is no longer actively maintained. It is provided as is, for anyone who may still be using these technologies, with no warranties or claims of accuracy with regard to the most recent product version or service release.

This section addresses issues relating to general security in the team solution. This may include Windows NT, SQL Server, and Access Workflow Designer row-level permissions.

For information about specific error messages, see Error Messages.

Security requirements and limitations

To secure your team solutions, it is important to consider the following issues:

  • All the users of a server containing Access Workflow Designer team solutions should log on using Windows NT authentication. Local SQL Server logins are not supported.

  • Microsoft Windows® 95/98 offline clients must log on using the MS Network Client option.

  • Because Windows NT caches user credentials and SQL Server is using Windows NT authentication, any changes made to a user’s Windows NT or SQL Server login accounts will not take affect until the user logs off and then logs back in. Therefore, if credentials are changed during an active connection, SQL Server only recognizes the new credentials after the user logs out and logs back in. For additional information about important issues concerning user login information, see Changing sa Password On the Client.

For more information about security requirements, see Security Permissions Model.

Insert and column permissions limitations

By default, any data changes on a data access page bound to an SQL view (for example, IssuesView in the Issue Tracking solution) send updates to the underlying table (for example, Issues).

When a table is added to the table hierarchy, the permissions provided depend on whether the table has a primary key defined. For example, if the table has a primary key and row-level permissions are enabled, then Update, Insert, and Delete permissions are provided by default on the base table. In addition, Select permissions are provided on the primary key columns of the base table, which makes it possible for updates. If the primary key does not exist, no changes are made to the table permissions.

Modifying permissions on the Issue Tracking solution

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