Microsoft KB Archive/249620

Knowledge Base

MOD2000: Error Message: Object Doesn't Support This Property or Method ... on Case-Sensitive Server

Article ID: 249620

Article Last Modified on 7/31/2001

---

APPLIES TO

• Microsoft Office 2000 Developer Edition

---

This article was previously published under Q249620

SYMPTOMS

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:

VBScript

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 OK, and then click the Permissions tab, you receive the following error message:

Internet Explorer Script Error

An error occurred in the script on this page. 

Line:    206
Char:    3
Error:   Object doesn't support this property or method: 'document.all(...).style'
Code:    0
URL:     http://<server>/<database>/itempermissions.htm

Do you want to continue running scripts on this page? 
                    

RESOLUTION

Use roles on a Microsoft SQL Server that is not case-sensitive.

MORE INFORMATION

Steps to Reproduce Behavior

1. Install Microsoft SQL Server on a server computer. Be sure to install a case-sensitive server.
2. Install the Access Workflow Designer server and developer components.
3. Deploy the Issue Tracking solution.
4. On the development computer, open the Issue Tracking project in Microsoft Access. On the Tools menu, point to Security, and then click Database Security.
5. Click the Database Roles tab. Click Add. Type Authors. Note the uppercase "A" on Authors. Click Application Role, and then click OK.
6. 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.
7. 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.
8. Click the Database Roles tab. Click Authors, and then click Edit. Click Permissions , and then assign the following permissions to the listed database object:
   
   

   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

9. 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.
10. 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.
11. Create a new issue, and then save it.
12. Edit the issue that you created in the previous step.
13. Click the Permissions tab. Click to select the Enable permissions for this item check box.
14. 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.

Additional query words: pra runtime object doesn t support this property or method

Keywords: kberrmsg kbbug kbpending kbworkflowdesigner KB249620

---

Send feedback to Microsoft

© Microsoft Corporation. All rights reserved.