This article was previously published under Q249620
This article has been archived. It is offered "as is" and will no longer be updated.
When you try to set permissions for roles in the Issue Tracking solution (that is included with Access Workflow Designer) on a case-sensitive Microsoft SQL Server, you may receive the following error message:
Your changes to the item permissions for this issue were not saved.
Object doesn't support this property or method: 'document.all(...).style'
After you click
, and then click the
tab, you receive the following error message:
Internet Explorer Script Error
An error occurred in the script on this page.
Error: Object doesn't support this property or method: 'document.all(...).style'
Do you want to continue running scripts on this page?
Use roles on a Microsoft SQL Server that is not case-sensitive.
Steps to Reproduce Behavior Install Microsoft SQL Server on a server computer. Be sure to install a case-sensitive server. Install the Access Workflow Designer server and developer components. Deploy the Issue Tracking solution. On the development computer, open the Issue Tracking project in Microsoft Access. On the Tools menu, point to Security, and then click Database Security. Click the Database Roles tab. Click Add. Type Authors. Note the uppercase "A" on Authors. Click Application Role, and then click OK. Click the Server Logins tab. Click Add. Add a SQL Server login for a specific DOMAIN\username. Remember this SQL Server login because you must use this login later. Click the Database Users tab. Click Add. Provide a database login for the user that you created in the previous step. Assign the user to the Authors role that you created in step 5. Click the Database Roles tab. Click Authors, and then click Edit. Click Permissions , and then assign the following permissions to the listed database object: Collapse this table Expand this table
Database object Permission Category SELECT CategorySorted SELECT Issues SELECT, INSERT, UPDATE, and DELETE IssuesBaseView SELECT, INSERT, UPDATE, and DELETE IssuesComments SELECT, INSERT, UPDATE, and DELETE IssuesCommentsView SELECT, INSERT, UPDATE, and DELETE IssuesGridViews SELECT, INSERT, UPDATE, and DELETE IssuesLinkedFiles SELECT, INSERT, UPDATE, and DELETE IssuesLinkedFilesView SELECT, INSERT, UPDATE, and DELETE IssuesProperties SELECT, INSERT, UPDATE, and DELETE IssuesView SELECT, INSERT, UPDATE, and DELETE IssuesWorkflow SELECT IssuesWorkflowActions SELECT Priority SELECT Resolution SELECT Status SELECT SubCategory SELECT SubCategorySorted SELECT modColumns SELECT modObjectTypes SELECT modObjects SELECT modPermissions SELECT, INSERT, UPDATE, and DELETE modProperties SELECT modUserList SELECT On a client computer, have the user that you created in step 6 log on. Connect to the server computer and install MSDE, SQL Server SP1, and the Access Workflow Designer client components. On the client computer, have the user that you created in step 6 log on and browse to the server computer's Issue Tracking solution database and the Gridview.htm page. Create a new issue, and then save it. Edit the issue that you created in the previous step.
Click the Permissions tab. Click to select the Enable permissions for this item check box.
Set the permissions for the solution roles as needed, and then click OK.
Note that you receive the error messages mentioned in the "Symptoms" section at the beginning of this article.
Article ID: 249620 - Last Review: October 20, 2013 - Revision: 1.1
APPLIES TO Microsoft Office 2000 Developer Edition
kbnosurvey kbarchive kbbug kberrmsg kbpending kbworkflowdesigner KB249620
Contact us for more help
Connect with Answer Desk for expert help.