Search options (Page 19 of 25)

Kim, As far as your decimal points are concerned, if you change the field type to REAL in the Database Tables tab within MVD, you should be able to enter in decimals past 2. I changed it in your project you attached and I was able to enter in values such as 1.2345 and it showed that way in the grid.

Forgive me for my denseness. I'm trying to understand the range searches and the calculations you want. It might help if you would do a screenshot of your form and make annotations on it and submit it here so we can get a better feel for how the form should work.

Sorry Adam. Rushed through the solution I guess. Try attached.

Project fixed. Since sales items belong to sales invoices and credit items belong to credit invoices, you no longer need the dbcr field in the sales items table. I removed it. I think you were getting confused with the timing of the "onAfterClick" event. From a parent form you were trying to manipulate properties on a subsequent form after the subsequent form was completed. Changing properties are typically (not always) done during the onShow event and OnChange events for an open form. Anyway, see if the attached project takes care of what you were trying to do.

Kim,  Either way is acceptable. There really is no one right way. The one that works for you is the right way. My personal preference is to just do it through code. But I would still define the index on the database. If you go the database route, you may want to consider intercepting the constraint error message through code. The system generated error messages are not the most user friendly. Users may be confused as to what happened. Dimitry has provided a solution in this forum on how to intercept the SQL exception message and replace it with your own. I keep a folder of helpful scripts from this forum that I can use as a reference when I need it rather than trying to find the topic in the forum. Here is a general script to intercept the SQL constraint message for the Unique constraint and replace it with your own message.

// The following is an example for Unique Constraint error

// global event for all exceptions related database 
function OnSQLException(Sender: TObject; Msg: string; SQL: string): boolean;
begin
    // Exception when you use the functions SQLExecute or SQLQuery

    if Sender=nil  then
    begin
        if Pos('UNIQUE constraint failed', Msg)=1 then
        begin
          result := true; // to prevent system message
          MessageBox('Record already exists', 'Error', MB_OK+MB_ICONWARNING); // your message
        end;
    end;

    // Exception from MVD save operation assigned to a button

    if Sender = Form1.SaveButton then    // if exception from Form1.SaveButton
    begin
        if Pos('UNIQUE constraint failed', Msg)=1 then
        begin
            result := True; // to prevent system message
            MessageBox('Record already exists.', 'Error', MB_OK+MB_ICONWARNING);
        end;
    end;
end;

Just substitute your Name and Surname fields where I have Col1 and Col2.

If SqlExecute('Select Count(Id) From MyTable Where Col1 = "' + Form2.Edit_Col1.Text + '" and Col2 = "'
      + Form2.Edit_Col2.Text + '"') > 0 then
      Begin
         MessageBox(Form2.Edit_Col1.Text + ' ' + Form2.Edit_Col2.Text + ' exist in the database.' + #10#13#10#13 + 'Duplicate record is not allowed - Cannot Save','Error',MB_OK+MB_ICONERROR);
         Cancel := True;
         Form2.Edit_Col1.SetFocus;
         Exit;
      End;

Kim, The example tcoton pointed out is an excellent example, but may be a bit more advanced for a newbie. I don't mean to insult your intelligence. If you understand that particular example, then disregard my example. I put together a very simple project for you to learn the concept.

Place your If statement in the password field (edPassword) OnChange event.

Adam, I went ahead and put in a timer so if the app is still running over midnight, then the recurring process will run and you'll see the new recurring expenses populated in the tablegrid. The timer checks every minute so if you are watching and it does not populate right at midnight, wait a minute and it will.

You do not need to restart the app. They should show after you do a save. Are you saying that they are not showing when you do a save? They do on my end. But if you want to place a dbUpdate in the script, don't create a button for that. Just place it inside the  "frmExpenses_Button_Save_OnAfterClick" procedure after the "If" statement.

I updated the project so you won't get the table not found on startup. Plus the save button will now catchup all recurring expenses for past dated recurring expenses and display them on the grid. I no longer empty your Recurring Boolean value and Recurring Every value. I let them alone so you can see that they are recurring expenses. However, I had to create another Boolean field in the Expenses table so I can check that field to see if a recurring record was created and turn it on if a recurring was created. The app, upon startup, will still check and create new future recurring expenses as their date arrives. I tested the app, but not necessarily an exhaustive test for time sake. If you start messing around with changing dates on past recurring expenses, there may be issues in the recurring process and possibly create duplicates. Therefore I disabled the expense date on past recurring expenses. I put some controls in place to try to prevent other problems. For instance, I do not allow a user to change the recurring date any longer. That date is controlled by the Recurring Every value and shouldn't be messed with. Try it out and give it a whirl.

Thank you Dimitry. That was quite obvious. I wasn't thinking along those lines for converting the date. Sometimes one can't see the forest for the trees :-)

Adam, the attached project has Dimitry's date fix and I put in what I think you want on a Save event. So  when saving a recurring event, the next recurring event will get populated and thus show on the tablegrid. From that point on the other process will keep up with recording future recurring expenses.