Hi Rod,
1. I was unable to assign the Date-field to a Integer-field and vice versa.
2. The MONTH($DATE$) + "/" + DAY($DATE$) + "/" + YEAR($DATE$) did not work
due to the Swedish date format
3. The equivalent Swedish version did not work either YEAR($DATE$) + "-" +
MONTH($DATE$) + "-" + DAY($DATE$)
Well, this was all some time ago, so I should better give it another try
with fresh versions of everything...
Best Regards - Misi, RRR AB, http://www.rrr.se
> Hi Misi,
>
> Don't give up!!!
>
>>The good things about the date-fields you mentioned was non-existing in
> my
>>case. I think this is due to the format "2006-01-31" which was
> interpreted
>>as an arithmetic operation (2006 minus 1 minus 31).
>
> Yes you can't do arithmetic with date string literals - pretty sure you
> need to use an integer literal that represents the number of days since
> 4713 BC. Assign a date field to an integer field to find out what it's
> integer equivalent is.
>
>>I could not even create an escalation that did a ('Datefield' $DATE$).
>
>>There were no workflow that allowed me (not even by using a temporary
>>char-field) to move the currend date into a Date-field.
>
> Yep you need to set fields the current $DATE$ to a character string via
> MONTH($DATE$) + "/" + DAY($DATE$) + "/" + YEAR($DATE$) first and then
> assign the date field to this character string. I guess the thing about
> this method is that there is no ambiguity about the date format.
>
> Regards,
>
> Rod
>
> _______________________________________________________________________________
> UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
>
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
