Changes done on the security type permissions on a visual studio privilege has a different result then changes done on the front end.

The idea would be to change the properties in visual studio on the security object type. We now only have one field with the enum read/update/delete/... I would be easier if we had read and update,... in separate properties as it shows on the front end.

The case where we encountered the problem, and where the idea came from is explained in here

The inconsistency was explained by MS as worked as designed. The bug we encountered results in different behavior between security changes on table permissions, form datasource permissions in the back-end and the front-end.