With NOW and DATEFORMAT dd according to the manual!

Bye
Marc

['AntragsID'] = DATEFORMAT(NOW(),"\Y") works for me, but its written in a textfield. Maybe value helps converting it to int?

Yes, definately value! ['bewilligtBisJetzt'] = VALUE(DATEFORMAT(NOW(), "\Y"))

I don't quite get what you mean by dimension Element, could you give an example of what you expect the rule to return?

Therefore you need to convert it to a string again:

['TestStrElem'] = STR(VALUE(DATEFORMAT(NOW(), "\Y")), 4, 0)

The result is. e.g. 2010 as a String.

Holger

I'm surprised that the combination VALUE + DATEFORMAT apparently works for you. The results in my system (newest version) is always Zero.

The functions separately are working correctly.

Nico

well, i am using palo 2.5

Hi. Looks like the 2.5 version is a bit more stable than more recent versions, or is that just a guess based on the above? Can this version still be downloaded? I find both 3.0 and 3.1 struggling to perform basic rules that are very easily handled in products available from competitors, e.g. a simple carry foward of a balance over months and years doesn't always return correct values, etc.... Is no-one else experiencing any of these issues, or is the commercial edition of Palo just so much more stable than the open source?

I would not really recommend to use 2.5 any more. No multi threading there, no 64 bit version... I would rather write bug reports to help the project proceed instead of relying on outdated versions.

bugs.palo.net/mantis/public/

The other Holger

By the way, I run version 4334 and your sample works for me, at least when the element is string.

Old thread, but this issue hit us using the open-sourced code for Palo (v3.1.1).

We fixed it, so if you're interested in the fix (which can be applied to the code from sourceforge), please PM me.

As you know that palo server return 0 while we convert date string to number like value(dateformat(now(),\d)). I read you article that it seems that you fixed the bug already.


Could you share it to me? the bug is really annoyed. Thanks for your support always and looking forward to hearing from you.


My palo is version 3.2