Search options (Page 1 of 34)

Cancel := True;

myvalue := Report.TableGrid1.Cell[1,viii].AsInteger;
or
myvalue := StrToInt(Report.TableGrid1.Cells[1,viii]);

http://myvisualdatabase.com/help_en/scr … egrid.html

There's nothing unusual there.
For ... loop that automatically changes the value to 1 until it reaches the condition value.
While ... loop while the condition is true. How much to change the value and when to do it depends on the user.
Used for increments other than 1 and other conditions.
In your example, there is no increment until the correct cell value is entered.
Repeat ... until - a cycle similar to the previous one but backwards.
The difference between the last two is that “Repeat ... until” will be executed at least once.
Therefore, in your case, the choice fell on WHILE.
In Konstantin's example there are essentially two "Repeat ... until" loops inside a "For".

Проверьте правильность имени события OnChange в свойствах таблицы.

P.S.
What BeginUpdate do?
This call prevent NextGrid from drawing EACH new or changed Cell until operation is finished. Also all complicated calculations needed for drawing Cell is skiped too. This can speed up your code a lot!

We will draw this rows ONLY after we finish with operation, and ONLY we will draw visible Cells on screen. After you finish with adding rows, ALLWAYS call EndUpdate.

Hi Jean,

A little higher in the post I posted the amorti-m1.zip version.

Here is the direct link. https://myvisualdatabase.com/forum/misc … download=1

Everything there is already tied to the EditBox where you can set your values.
Indicate your final formula and I will add it instead of mine. Yesterday I looked at calculators online and they all calculated using your formula.

Hi Adam

I don't understand what algorithm you are trying to achieve.
Why then StartDate, StartTime? Why are the signs of message or sound output automatically removed immediately after one trigger? No more reminders needed? Maybe I haven't studied the project well enough?

I'll shorten my question.
You have StartDate, StartTime, DueDate, DueTime. For which Start or Due event should the reminder be triggered?
Right now you are checking (DueDate <= current date) and (message OR sound are 1).
The second part of the test (message OR sound equals 1) is already incorrect. It causes both message output and audio output to be executed even if only one of them is enabled.
Find answers to the questions for yourself and adjust the condition check.

You should decide what criteria to use to check records in the OnTimer procedure.
You have the following fields StartDate, StartTime, DueDate, DueTime, PlaySound, MsgPopup, taskCompleted. Which fields should be included in the verification and under what conditions. Moreover, checking for messages and sound should be separated separately.

Hi,

both options are possible
Here is an example for SQLite.
Example1 - script query, Example2 - Buttom SQL query.
Replaced SQLite DLL with a new version.

Example of calculation taking into account days in a month.
I would like to draw special attention to the fact that bank calculations may differ.

Hi Adam

Your "datetime" field in the "Remainder" table is always NULL and I did not find where you should set it. Check the query condition in the procedure OnTimer;:

duedate Is Not Null and datetime Is Not Null and Date(duedate) <= strftime('%Y-%m-%d', 'now','localtime')
...
and strftime('%H:%M', Time(datetime))

You can simply use Date(''now'',''localtime'') instead of strftime(''%Y-%m-%d'', ''now'',''localtime'')

"But even when the moon looks like it’s waning…it’s actually never changing shape. Don’t ever forget that." —Ai Yazawa

Hi Derek,
Thank you.

samtorn, for self-study.
Option for FastReport. Directly for the Memo field on the form.
Create Memo2 next to Memo1 in Derek's example and place the code below.
It looks scary but it's simple.

[IIF(<Report."Employer_Hours.dayofweek">=1,'Mon',
IIF(<Report."Employer_Hours.dayofweek">=2,'Tue',
IIF(<Report."Employer_Hours.dayofweek">=3,'Wed',
IIF(<Report."Employer_Hours.dayofweek">=4,'Thu',
IIF(<Report."Employer_Hours.dayofweek">=5,'Fri',
IIF(<Report."Employer_Hours.dayofweek">=6,'Sat',
'Sun'))))))]

OR

[SQLExecute('SELECT CASE '''+<Report."Employer_Hours.dayofweek">+'''*1 WHEN 1 THEN ''Monday'' END ')]

And a link to the manual to make it work: https://www.fast-report.com/public_down … ual-en.pdf

You can use a calculated field like

CASE <FIELD Name> 
WHEN 0 THEN 'Sunday' 
WHEN 1 THEN 'Monday' 
WHEN 2 THEN 'Tuesday' 
WHEN 3 THEN 'Wednesday' 
WHEN 4 THEN 'Thursday' 
WHEN 5 THEN 'Friday'
WHEN 6 THEN 'Saturday' END

or in the FastReport script like

begin
   case <variable name> of
      1: Form1.Edit1.Text := 'Sunday';
      2: Form1.Edit1.Text := 'Monday';
      3: Form1.Edit1.Text := 'Tuesday';
      4: Form1.Edit1.Text := 'Wednesday';
      5: Form1.Edit1.Text := 'Thursday';
      6: Form1.Edit1.Text := 'Friday';
      7: Form1.Edit1.Text := 'Saturday';
   end;
end;

In addition, Pascal and SQLite have their own functions for determining the day of the week (day number) by date.
DayOfWeek()
And
strftime('%w', ...).