Heres another tip.
Do this test in a backup (or a Test) database .
When running BS429, Check the checkbox
Show skipped records so you can see better what is going on.
Ive set up a monthly standing order to be paid on the 15th.
I set the start date to Nov last year.
I ran BS429 on 1st March 17.
As expected, it showed 4 due items:
- 15th Nov
- 15th Dec
- 15th Jan
- 15th Feb
I skipped 1,2 and 4 above and processed ALL - resulting in only 15th Jan being processed.
I restarted BS429.
It showed the item 15th Feb ONLY in the due list, even though it was skipped.
1) and 2) have now been permanently skipped, since 15th Jan was processed.
I still want to skip Feb.
I set the date picker to 16th March (so it now shows 15th March as due.
a) I skip 15th Feb and b) I process 15th March.
When I restart the program the date picker defaults to todays date 1st March.
15th Feb appears as Due.
Why?
Because (currently) it doesn't check for processed transaction past todays date.
BUT:
If I (again) set the Date Picker to 16th March - the list is empty - nothing is due.
Why?
Because the program now checks for processed transactions up to 16th March, sees the 15th March transaction is processed.
It then knows I have skipped anything before that date and shows an empty list.
OK, all a bit difficult to follow perhaps.
I will work on the program to improve the Skipped S/O's feature.