Search options (Page 3 of 34)

Yeah, actually I renamed the topic since we cannot interact with the frmdbCoreUsers.gridusers and actually it makes no sense to play with it since  the main issue is in the role combobox filtering in the frmdbCoreUserForm.

If the application has been compiled with a specific role and the role is deleted from the database afterward via sqlitestudio to hide it, the role will reappear in the database with a new id at next app launch. I do have buttons and fields reserved to developer in my app and I want to avoid anyone else to play with them. Without this restriction I must keep 2 versions of the app, 1 with the hidden dev features as well as no dev permissions and 1 without any of the dev features which is cumbersome.

It looks like the frmdbCoreUserForm combobox is a dynamic component and I don't get how to filter it.

Thanks guys.

@k425, I have downloaded the current available version of clearapp and I don't see the last line which you show on your screenshot.
I cannot read Russian but there is an absolute link instead of relative link to ".\Script\Tools\Dbg\resourses\clear.png" when clicking on the second item of first menu in the main form.

Yeah but the price of the product for commercial use is just prohibitive!!! I have thought of integrating some python script within MVD to do exactly the same thing but for free I am still working on it...

Except for the xml file, is there any other feature worth using the unofficial 6.61beta?

Is there a simple way to ask the user for the file path and name of his/her choice via an explorer window instead of having a fixed path for "FileName"?

So... I have been struggling quite a bit with the duplicate checking on records already existing when updating and I finally found something that works.

The above works well for a new record but it blocks any update on existing records considering an edit as a systemic duplicate.

My form has a double function of inserting new entries and displaying existing records so, the "show record" and "new record" do not behave as expected, especially the "show record" that requires to double-clic twice (4 clicks) to retrieve the current id/generated id.

If someone has the same kind of issue, here is the fruition of a long battle and some headaches.

The key is in the operator != which compares the values left and right and returns a false instead of the <> which returns a true and with SQL all conditions must be true to get a true result. If at least one condition is false then the result could be either false or incomplete, This is why it did not worked for updates since the result was always true, hence duplicate alert. In a new record, the ids old (-1) and new (next id number) are different while when updating, the ids are the same. SQLite creates internally an "old.id" and a "new.id" before each transaction, those can also be used in triggers and are used for internal rollback.

procedure Form_SaveButtonName_OnClick (Sender: string; var Cancel: boolean);
var id: integer;
begin

  if  (SQLExecute ('SELECT COUNT(id) FROM table WHERE (column COLLATE NOCASE ="'+Form.TextBox.Text+'") and (id!="'+inttostr(Form.SaveButtonName.dbGeneralTableId)+'")')) > 0 then
     begin  // Replace <Record> by proper descriptive field
          MessageDlg('This <Record> already exists:  ' +Form.TextBox.Text +#13+'Entry canceled', mtError, mbOk, 0); // Displays a red 'X', header is: Error
          Cancel := True;
          end
          else
          begin
           MessageDlg('This <Record> has been saved:  ' +Administration.Administr_WinID.Text, mtInformation, mbOk, 0); // Displays an Info icon header is: Information
          Cancel := False;
     end;

end;

That is what the collate nocase does!

Got it, to check case insensitive duplicates, use COLLATE NOCASE:

function DupliChk (sTable, sField, sValue: string;): boolean;
var d: string;
begin

    d := SQLExecute ('SELECT Count(*) FROM '+sTable+' WHERE '+sField+' COLLATE NOCASE = "' + sValue + '"');
    if StrToInt(d) > 0 then result := True else result := False;
end;

It works until someone tries to cheat it with a space before or after the entry...

I transformed your solution into a function as it is easier when used repeatedly. It works perfectly when using a form that was not called by a "New Record" button.

function DupliChk (sTable, sField, sValue: string;): boolean;
var d: string;
begin
    result := False;
    d := SQLExecute ('SELECT Count(*) FROM '+sTable+' WHERE '+sField+' = "' + sValue + '"');
    if StrToInt(d) > 0 then result := True;
end;

And the usage is:

procedure Form_ButtonSave_OnClick (Sender: string; var Cancel: boolean);
begin

   if DupliChk('Table','Column',Form.EditBox.Text) then
     begin   //replace object by self-explanatory text
          MessageDlg('This object already exists:  ' +Form.EditBox.Text +#13+'Entry cancelled', mtError, mbOk, 0); // Displays a red 'X', header is: Error
          Cancel := True;
          Form.EditBox.Clear;  
     end;
end;

Thanks pavlenko.vladimir.v, that looks so simple, I feel dumb.

There is a RTF memo component, the one with a little red A.

This method works only when using a "New Record" button, it does not work with a "Save Record" button.

I tried to add the Action='SaveRecord' but it might be another string sent when using a "Save Record" button:

..[snip]....if (Action = 'NewRecord') or (Action='SaveRecord') then....[snip]....

Does anyone knows what the string sent is?