Date fields are really number fields that store the number of days since 12/31/0000. You can add and subtract them just like numbers and the displayed dates will adjust automatically when the end of a month or year is reached.
Next_Day can simply be defined as: CreatedDateField + 1 and the return type for the calculation field can be set to return "date" as it's return type.
IF the creation date is 3/31/2011, next day will compute and return 4/1/2011 (using MMDDYYYY date formats in this example.)
Hi phil , Thanks for your response. I made it work. another problem. I have attached the snap shot for your consideration.
What i did:
I created the Calculation field with case function. because i need to calculation based on few parameters which user has input. I think i got it work.
My problem :
lets say Mr X want to pay jun/1/2011 to sep/1/2011. practically 4 turns . Now i have 12 calculation fields which is calculate set of next payment dates according to created day. If i want to see only the dates between start date and end date , what should i change in the calculation field?
This is the Calaculation i use now
Case ( frequency="Monthly" ; Date ( Month(startdate) +1 ; Day(startdate) ; Year(startdate) ) ; frequency="3 Month " ; Date ( Month(startdate) +3 ; Day(startdate) ; Year(startdate) ) ; frequency="6 Month " ; Date ( Month(startdate) +6 ; Day(startdate) ; Year(startdate) ) ;0 )
I'd be inclined to use a portal for the payment dates. A script could use the frequency and a single date calculation to generate the payment dates in the portal's table.