How to disable Write/create/delete

Posted by goo on 03-Sep-2018 04:53

Progress 91d07

The customer has a database that they want to Close for update, so only read should be possible. 

I add a user in the securitylist, that is named Reader, and I update the Security-data-list 

CAN-WRITE:!Reader,*

CAN-DELETE:!Reader,*

CAN-CREATE:!Reader,*

CAN-LOAD:!Reader,*

I startup the Client With -U Reader -P ReaderXXX,

but still I am able to create a record for the table I have updated the Security.

What am I doing wrong? Is there an easier way to Lock the database? 

//Geir Otto

Posted by goo on 03-Sep-2018 09:24

It seems like a restart of the db made it work….but I also added -RO … just to be sure...

All Replies

Posted by hjboxem on 03-Sep-2018 05:03

Use the -RO as a client startup parameter.

Also see: knowledgebase.progress.com/.../P22224

Posted by George Potemkin on 03-Sep-2018 05:06

Did you set Admin -> Database Options -> Use Runtime Permissions Checking ?

Posted by goo on 03-Sep-2018 05:12

No, that I didn't ….

I saw the -RO, but after Reading I got the impression that I could not use it against a multiuser database?

Posted by hjboxem on 03-Sep-2018 05:17

You'd probably want to access the database in single-user mode, otherwise the users will get the warning that the BI is not truncated. In this way it is also possible to connect with multiple users.

Posted by George Potemkin on 03-Sep-2018 05:19

The -RO option will not use a connection through shared memory but it can be used with the remote connections.

Runtime Permissions Checking is what you need if you like to use the permissions defined for the tables.

Posted by goo on 03-Sep-2018 05:46

I can't find the Use Runtime Permissions checking for the 91d07 database.... is this something that came in a later Version?

Posted by George Potemkin on 03-Sep-2018 06:02

Use Runtime Permissions checking is available since V10.1A:

knowledgebase.progress.com/.../P125990

Posted by goo on 03-Sep-2018 06:13

I thought so....

Posted by goo on 03-Sep-2018 09:24

It seems like a restart of the db made it work….but I also added -RO … just to be sure...

This thread is closed