Due Date Based on Purchase Date (1 Viewer)
- Thread starter vcarrill
- Start date
- Local time
- Yesterday, 17:19
- Joined
- Oct 29, 2018
- Messages
- 21,467
Hi. One way is to use the fAddWorkdays() custom function. For example:
(I could be wrong with the syntax.)
Code:
Me.DueDate=fAddWorkdays(7,Me.PurchaseDate)Very important questions; will you need to deal with holidays?; When does the "Next day" start?; How often will data be entered that should actually be considered as "On the next day?"; Can the due date be changed after it is created?
Working with due dates can become very messy if you don't find all the conditions that can affect it. This is very important when you start seeing data put in after "business hours" that is expected to be dealt with one day later than your program expects or "needs to be adjusted" based on other criteria.
Working with due dates can become very messy if you don't find all the conditions that can affect it. This is very important when you start seeing data put in after "business hours" that is expected to be dealt with one day later than your program expects or "needs to be adjusted" based on other criteria.
Hello,
The due date is an "estimate" only.
Example: Purchase Date Monday 11/4/19
Due Date would be 11/13/19, not including weekends on a basic Mon - Fri work week.
Holidays may offset this date, but since it is an estimate I think it would be acceptable. I am looking for a general date to be expecting the delivery of the item.
The due date is an "estimate" only.
Example: Purchase Date Monday 11/4/19
Due Date would be 11/13/19, not including weekends on a basic Mon - Fri work week.
Holidays may offset this date, but since it is an estimate I think it would be acceptable. I am looking for a general date to be expecting the delivery of the item.
- Local time
- Yesterday, 17:19
- Joined
- Oct 29, 2018
- Messages
- 21,467
First, did you download the file from the link I posted?
- Local time
- Yesterday, 17:19
- Joined
- Oct 29, 2018
- Messages
- 21,467
Yes, and make sure you leave the name as Module1 (or something similar). Also, please double check the syntax. I wasn't sure if the number comes first or later. Let us know how it goes.
Ok, I did as instructed and copied the material under Module 1.
I entered:
Me.DueDate=fAddWorkdays(7,Me.PurchaseDate) in the AfterUpdate event of Purchase Date.
When I entered 11/4/19 under Purchase Date, the Due Date says 10/20/2067.
I entered:
Me.DueDate=fAddWorkdays(7,Me.PurchaseDate) in the AfterUpdate event of Purchase Date.
When I entered 11/4/19 under Purchase Date, the Due Date says 10/20/2067.
- Local time
- Yesterday, 17:19
- Joined
- Oct 29, 2018
- Messages
- 21,467
Hi. Did you verify the syntax like I said? I don't have a copy of the file to verify for you. Can you maybe post the function declaration?
- Local time
- Yesterday, 17:19
- Joined
- Oct 29, 2018
- Messages
- 21,467
Hi. I had it backwards. Try the new syntax I just posted above and let us know what happens.
- Local time
- Yesterday, 17:19
- Joined
- Oct 29, 2018
- Messages
- 21,467
Hi. You're welcome. Good luck with your project.
