Search options (Page 20 of 25)

It only creates new recurring expenses at application startup.

If you changed your date format to MM/DD/YYYY then just go back to Recurring Expenses 3.zip and use that project.

Hmmm....Not sure what's going on. How far back did you make the date for the daily expense recurrence. If you go back years, it will create an expense record for each day from that date forward till tomorrow. And if you do that for multiple expenses it will take some time to insert/update records before the app shows the first form. I tested a single daily recurrence and went back a full year, which is highly unlikely in real life.  It took maybe 20 seconds or so before the first form shows, but it did not crash or anything like that. And the app restarted fine. Try emptying your database and start fresh again.

It looks like you are getting the error when you are adding an expense simultaneous to paying it, which is fine. The qty appears to be empty which is causing the error.  I would assume this should never be the case, but to fix this particular situation you can set the default value to 0 for Qty on your Expense form

image host

That might work for the first time of the expense, but it still does not answer when to create the next expense. I didn't want to leave you hanging so I incorporated the trigger based on an expense being paid. In the attached project, there is a button called Paid. Upon clicking this button the expense will be identified as Paid and if it is a recurring expense then the next expense record will automatically be created. The date of the next expense is based on the recurring every... combobox.  Hopefully this will help set you in the direction you want.

Change the cancel button code to the following.

procedure frmStudent_btnCancel_OnClick (Sender: string; var Cancel: boolean);
begin
    End_Data := Load_Record_String(frmStudent);
    If Start_Data <> End_Data then
      Begin
        If MessageBox('Changes were made to the data on this form.'+#13#10#13#10+ 'Are you sure you want to cancel changes?','Confirm',MB_YESNO+MB_ICONQUESTION) = IDYES then
          Begin
             if frmStudent.dbAction = 'NewRecord' then
              begin
               SQLExecute('DELETE FROM checks WHERE id_Student='+IntToStr(frmStudent.btnSave.dbGeneralTableId));
               SQLExecute('DELETE FROM student WHERE id='+IntToStr(frmStudent.btnSave.dbGeneralTableId));
              end;
              frmStudent.Close
          End else
          Begin
          frmStudent.btnSave.SetFocus;
          Cancel := True;
          Exit;
          End;
      End;
end;

Also, I noticed you changed the name of the cancel button so you need to use the On_click procedure name above.

One more thing. The method of comparing changes I showed you will work for all top level forms (such as frmStudent in your case), but if you have a lower level form (a child form such as frmCheck in your case) off of the main form and you want to use the same methodology for checking at cancel time, then you will need to define separate global variables for the lower level form (something like Chk_Start_Data and Chk_End_Data) and change the names in the cancel button procedure.

Adam, See if the attached is what you are looking for. The method to my madness is to load all the fields on a form into one string. I created a function to do this. You then call this function at the On_Show event of any form and hold the result into the Start_Data string varialble. You then call the function again on the On_Click event of the Cancel button and hold the data in the End_Data string. You just compare the two strings on the Cancel button event and produce a message if they do not compare equally.

This method will not handle images stored in the database. You will need to handle images separately by holding the image at the start of the form and then check it when you click the Cancel button.

Here is an example. See attached.

No problem Adam.  Actually I learned something new in putting this together for you. You can declare global report variables in FastReport Code tab. These variables can be used/manipulated and printed anywhere in the report. A good example of this would be when you want to repeat or use group header data in a group footer.

Not sure if this answers your question. But there isn't anything that MVD does automatically to upgrade database tables for users. What I do is create a separate MVD program. The only thing this MVD program does is run a script similar to the following:

SqlExecute('ALTER TABLE MyTable RENAME TO TempTable');
    SqlExecute('CREATE TABLE MyTable ('
      + 'id               INTEGER PRIMARY KEY ASC,'
      + 'Field1    TEXT,'
      + 'Field2    TEXT,'
      + 'Field3    TEXT,'
      + 'NewField  TEXT)');

    SqlExecute('INSERT INTO MyTable ('
                            + 'id,'
                            + 'Field1,'
                            + 'Field2,'
                            + 'Field3) '
                        + 'SELECT id,'
                            + 'Field1,'
                            + 'Field2,'
                            + 'Field3 '
                    + 'FROM TempTable');
    SqlExecute('DROP TABLE TempTable');

I use a third party install software to install the upgraded MVD application (without the database). The same install process then installs and runs the MVD database table upgrade program (script above). After the installation the database table upgrade MVD program is deleted because it's not needed any longer. One thing you have to pay attention to is making sure that the "server" setting in the settings.ini file in the database upgrade folder is pointing to the installed application database. My install process does this automatically so the user does not need to do anything. The whole thing is pretty seamless from my standpoint. Hope this helps.

Adam, when you copied Dimitry's code from Groups you missed replacing a variable in the following line:

frmInvoice.cbCustomer.Text := s_cbGroups;

It should be

frmInvoice.cbCustomer.Text := s_cbCustomer;

Adam, your combobox filter needs to include the first name. Replace your frmInvoice.cbCustomer.dbFilter with the following:

frmInvoice.cbCustomer.dbFilter := '(lastName LIKE ''%'+ s_cbCustomer +'%'''+') or (firstName LIKE ''%'+ s_cbCustomer +'%'''+')';