Hello,
Sometimes I get an incorrect Date Format in report using %u001, %u002 or %u003 in report fields. The field is in utc date time (tcdate) an instead of editing the date with the format '05.29.2013', the date is printed like 'May%x05'.
Thanks in advance for any help

This is from the Prog. Guide.

Dates
| Suppose date format 002 is: "year/month/day in month"

string result(80)

result = sprintf$("%D002", 727168)

| result contains "1991/12/2"

| Example of substitution symbol %D(format)

string result(80)

result = sprintf$("%D(Date: %02d/%02m/%04Y)", date.num())

| result contains "Date: 12/07/1993"

result = sprintf$("Date: %D(%02d %-20H %04Y)", date.num())

| result contains "Date: 12 June 1993"

UTC dates and times
| Date format 002 is "year/month/day in month"

| Time format 001 is "12 hour format:minutes:seconds AM/PM symbol"

string result(80)

result = sprintf$("%u002 %001", utc.num(), utc.num())

| Result contains "1997/01/01 10:02:53 pm"

string result(80)

result = sprintf$("UTC: %u(%02d/%02m/%04Y) %U(%02h%x%02m%x%02s %a)", utc.num(), utc.num())

| result contains "UTC: 22/07/1997 06:24:53 am"

| provided that for the user's language the time

| separator is ":" and the AM symbol is "am"

| Using a comma after a %u substitution symbol

string result(80)

result = sprintf$("%u001, ,Message text....", utc.now())

| result containts "06-05-15,Message text...."

We have the same problem with our customer.
We have opened an incident to INFOR.
The answer is:
"We have identified that on Windows environments the runtimefile "datecurr" sometimes, for some reason, is not read correctly.
We have been working hard to identify and are currently testing a new nbshell.
We hope to deliever a solution for this with the next portingsetrelease, scheduled for the beginning of July."

As soon as possible, I will let you know news.

Bye

Max

Ok, thank you very much for your answer, and let me know as soon as you get any solution.
Bye,
Philippe.

Hello,

We are experiencing the same problem with date format (e.g. November%x11) displayed in reports.

Would you have the solution by now ..? :-)

Thank you for your help

Merci from France

Bertrand