I have recently created a new user in GP and given them the SQL permissions to allow this new user ID to setup users and grant permissions. Effectively, this new user ID is going to 'act' as the sa user. My only issue with this is that the Org. Structures (Account Level Security) button at the top of the User Setup window is greyed out. It is available for DYNSA and sa, but not for my new 'super' user.
I have given this user 'Poweruser' status, and verified that all the Org. Structures permissions have been granted from the from the system perspective too.
Any ideas how I can get this resolved?
My experience is that won't work including your 'super user' group and desire to have those users act as 'sa' but others will probably have more detailed responses..
You will be constrained by the business logic when performing SQL tasks regarding users and access regardless of your underlying permissions. I have never seen what you are trying to do work.
Best of luck on this.
Thanks Tim, that was what I suspected. I find it odd that my 'super user' is able to do most everything, with this one exception. I wonder what the logic is behind that? It seems to me that if the ability to create a 'super user' exists, which it does, why would they limit this one functionality? I would love to hear from Microsoft on that.
Thanks for taking the time to reply. Given where we are now with SQL as the GP DB of choice I would think they wish they engineered this differently but at the time, certainly at the time I started with the product,. it was a product which had database Independence and ran on quite a few DB products including the MacIntosh. At the time MS-SQL was just a next gen of the sybase product and itself (don't remember the version, I think SQL 4.0) quite a pain in the a.. to work with. Things got much better with SQL 5 but the admin functions really haven't changed as they needed to be platform independent.
There are places in the Dexterity code where it checks for the user ID. It is specifically looking for 'sa' or 'DYNSA', there's no way around that. It's essentially 'hard-coded' into the program.
Leslie Vail, CPA, MVP, MCT, MCITP, MCP, MCITSASCI, Inc. * PO Box 600965 * Dallas, TX 75360 * 972-814-8550 * email@example.com
Other Microsoft Sites
I'm a Customer
I'm a Partner
Use the official Twitter tags:
#MSDYNCOMM | #CONV13