can it be that there are problems with Sentry plugins in the Windows client under SuperOffice 8.0?
We have an existing Sentry plugin, which our customer has been using since SuperOffice 7.1.
updated to SuperOffice 8.0. One of the rules the module should enforce is that
certain users are not allowed to create new companies.
In SuperOffice 7.1 we used the following code for this purpose:
public void GetTableRights (int AssocId, int GroupId, int RecordId, string TableName, ref object RecordData, ref bool o_CanInsertRow, ref bool o_CanReadRow, ref bool o_CanUpdateRow, ref bool o_CanDeleteRow, ref string o_ToolTip)
if (TableName. ToLower () == "contact")
o_CanInsertRow = false;
o_ToolTip = "yor are not allowed to add new companies.";
In SuperOffice 8.0, however, the GetTableRights method is no longer called when accessing the company card. Instead, we implemented a NetServer ContactSentry as follows:
public void ModifyTableRights (TableRights)
var rightsIterator = rights.Keys.ToList ();
foreach (TableInfo tInfo in rightsIterator)
var newRight = new TableRight (ETableRight.UDR);
if (tInfo.DbName == "contact")
rights[tInfo] = newRight;
In the SuperOffice 8.0 web client this works fine. The New button is grayed out as desired in the company context.
In the Windows client, however, the Sentry has no effect at all. The ModifyTableRights Code
is executed and the TableRight is also set. However, it has no impact on the client.
This function is crucial for our customer to perform the update to SuperOffice 8.0.
Furthermore, other restrictions - for example read-only- also have no
impact on the Windows client. The companies can still be deleted and edited.
Here too, it works perfectly in the web client.
Do we miss anything? Also, is there a current overview of which parts of the Windows client still use the old COM Sentry and which ones are using the NetServer Sentry?
With kind regards