>I am having a problem with Security on a SQL Server install. On the Users Form, Access Tab everything works fine until I change the access level of a control. Then when I select another control, the access level does not reflect the true setting, it continues to display the value of the last changed control. So if I had 3 controls called A, B & C and there currently wasn't any security set for this user, they would all defualt to FULL. Let's say I change B to be READ ONLY, when I then click on A, it displays READ ONLY as well. In stepping through the code, this is what I found:
>
>1. When I change the access level, the SetControlAccess method of the SecurityOBJ gets called
>2. If the control is not found in the v_usergroupsecure view, it calls a This.oBizObj.New
>3. From that point on, when I select a different control, the GetAccess method of the SecurityObj is failing on the Seek. Therefore it continues to return the previous value.
>
>When the seek fails, it calls the error routine in the cSecurityRulesFullAccess class with error # 1526 (ODBC connectivity error). After getting the error, I realised there are stored procedures for the users, groups and usgrlink tables. How should these be handled when switching from local to remote? Do you think this is the source of the problem?
>
>Kind Regards,
>
>Mat

Mat,

At some point I put a post for handling the stored procedures for SQL Server. You will need to add this to database. Let me know if you can't find it, and I'll email it to you directly.