Hi Tim,

I am a little puzzled about the Configuration "database". In my application
users can be added, deleted and altered. So far, no problem. They can also
be assigned roles. Again, no problem. I would also like to add, delete and
alter roles, which works for my database, but it does not for the
Configuration "database", because I receive error # 200.

When running this query

SELECT * FROM DatabasePrivileges
WHERE Name = 'Configuration'
AND GrantedTo = 'Administrators' --> BTW this is the role, not a user

the result is that the Administrators role has Select, Create, Alter, Drop,
Maintain, Backup and Restore rights.

The # 200 error prohibits me from granting and revoking rights to roles with
regard to the Configuration "database" such as the following query

GRANT UPDATE
ON DATABASE "Configuration"
TO "Administrators"  --> BTW this is the role, not a user

Currently there are 3 "standard" roles: Administrators, System and Public.
If I would add a new role, such as testrole, the # 200 error is still
received.

GRANT ALTER
ON DATABASE "Configuration"
TO "testrole"

The role "testrole" does not have any rights, yet. But right cannot be
added. I used the ALTER right this time (as opposed to UPDATE because the
Administrators role has it too, so it must be a valid right to add). This
means I cannot make new roles regarding the Configuration "database".

Did I do something wrong or is it just not possible? If not, could you
please explain why?

I am no SQL guru, far from it. With DBISAM I never used it. I am learning
and slowly but surely will get there, but this issue really puzzles me. You
may be wondering why I want to alter / add roles regarding the Configuration
"database". Well, I want a role that has only Maintain, Backup and Restore
rights, for example.

I hope my questions are clear. It would be easier if you would understand
the Dutch language  

Thanks in advance for your help.

Best regards,
Fons Neelen
The Netherlands, Europe.

Fons,

<< I am a little puzzled about the Configuration "database". In my
application users can be added, deleted and altered. So far, no problem.
They can also be assigned roles. Again, no problem. I would also like to
add, delete and alter roles, which works for my database, but it does not
for the Configuration "database", because I receive error # 200. >>

You can't modify anything about the Configuration database directly - it is
there for read-only purposes only as information about the system
configuration.  To modify its contents, you would use DDL statements against
the various objects that are in the configuration.

<< I hope my questions are clear. It would be easier if you would understand
the Dutch language  >>

Well, my daughter already knows French and German pretty well, and will be
working on a couple of more languages.  Now if I can just convince her to
work for me.

--
Tim Young
Elevate Software
www.elevatesoft.com

Hi Tim,

> You can't modify anything about the Configuration database directly - it
> is there for read-only purposes only as information about the system
> configuration.  To modify its contents, you would use DDL statements
> against the various objects that are in the configuration.

Sorry, but I don't quit follow. The GRANT statement is a DDL statement, so
why does this SQL statement not work as I think it should work  

GRANT UPDATE
ON DATABASE "Configuration"
TO "Administrators"

I am just trying to add the UPDATE right to the Administrators role on the
configuration database. The SQL statement seems to be correct apart from the
# 200 error.

Could you show me an example of how to this the right way? It will be much
appreciated.

Best regards,
Fons

Hi Tim,

You don't have to answer the question anymore. The configuration database is
like a blue print for the "real" databases, where the system defined roles
from the config database are copied to the "real" database and within this
"real" database one can modify the rights of these copied roles as desired.

If this is wrong, well, then please let me know.

Best regards,
Fons

Fons,

<< You don't have to answer the question anymore. The configuration database
is like a blue print for the "real" databases, where the system defined
roles from the config database are copied to the "real" database and within
this
"real" database one can modify the rights of these copied roles as desired.
>>

Correct.  All of the "system" objects, such as the Configuration database,
the System user, the Administrators role, etc. are not directly modifiable
because they each have a special purpose and meaning that cannot be changed.

--
Tim Young
Elevate Software
www.elevatesoft.com