Access - Manual Date Calculator

[Guest]

Anyone who can help!

I need help setting up a manual date calculator in my access program
(Example)
Fixed Date: 1/1/2008
Add 180 days - 6 months since original order
Add 30 days - 30 days extended
New Date: 4/22/2008

My goal is to be able to manually calculate the dates needed to contact
customers 30, 60 or 90 days or further out by just putting in a number and
having the program start with my fixed date and then add the new numbers to
give the extended date. I’ve used the dateadd function but that requires
going into the program and manually re-fixing the date add time. I have
times where there are multiple date changes needed at times. My program is
setup for multiple users and I don't want them going into the program
language and changing important access language for functionality of the
program.

Any help would be greatly appreciated.

D.F. Pierce

 

[Pieter Wijnen]

Does not!
Unbound Control: =DateAdd("d",[FixedDate], Nz([VarDays],0))

if You need more control

Unbound Control: =MyDateAdd([FixedDate], Nz([VarDays],0))

Where MyDateAdd is a public function accepting two variables

HTH

Pieter

 

[Guest]

Pieter:

Thank you for the information. It was helpful. Question - If I wanted to
add more than one variable date how would I set that up? If I had two or
more unbound control boxes how do you write the language to have more than 1
Nz([VarDays] account in the final NEW DATE.

Thanks again! Your instructions were easy to follow and timely.

D.F. Pierce

Does not!
Unbound Control: =DateAdd("d",[FixedDate], Nz([VarDays],0))

if You need more control

Unbound Control: =MyDateAdd([FixedDate], Nz([VarDays],0))

Where MyDateAdd is a public function accepting two variables

HTH

Pieter

Anyone who can help!

I need help setting up a manual date calculator in my access program
(Example)
Fixed Date: 1/1/2008
Add 180 days - 6 months since original order
Add 30 days - 30 days extended
New Date: 4/22/2008

My goal is to be able to manually calculate the dates needed to contact
customers 30, 60 or 90 days or further out by just putting in a number and
having the program start with my fixed date and then add the new numbers
to
give the extended date. I've used the dateadd function but that requires
going into the program and manually re-fixing the date add time. I have
times where there are multiple date changes needed at times. My program
is
setup for multiple users and I don't want them going into the program
language and changing important access language for functionality of the
program.

Any help would be greatly appreciated.

D.F. Pierce

 

[Pieter Wijnen]

Unbound Control: =DateAdd("d",[FixedDate], Nz([VarDays1],0) +
Nz([VarDays2],0))

HTH

Pieter

Pieter:

Thank you for the information. It was helpful. Question - If I wanted to
add more than one variable date how would I set that up? If I had two or
more unbound control boxes how do you write the language to have more than
1
Nz([VarDays] account in the final NEW DATE.

Thanks again! Your instructions were easy to follow and timely.

D.F. Pierce

Does not!
Unbound Control: =DateAdd("d",[FixedDate], Nz([VarDays],0))

if You need more control

Unbound Control: =MyDateAdd([FixedDate], Nz([VarDays],0))

Where MyDateAdd is a public function accepting two variables

HTH

Pieter

Anyone who can help!

I need help setting up a manual date calculator in my access program
(Example)
Fixed Date: 1/1/2008
Add 180 days - 6 months since original order
Add 30 days - 30 days extended
New Date: 4/22/2008

My goal is to be able to manually calculate the dates needed to contact
customers 30, 60 or 90 days or further out by just putting in a number
and
having the program start with my fixed date and then add the new
numbers
to
give the extended date. I've used the dateadd function but that
requires
going into the program and manually re-fixing the date add time. I
have
times where there are multiple date changes needed at times. My
program
is
setup for multiple users and I don't want them going into the program
language and changing important access language for functionality of
the
program.

Any help would be greatly appreciated.

D.F. Pierce