timestamps

building reports desktopintelligence
1

I have trouble with date timestamps.

Date format i regional setings are - yy.mm.dd . So when I want create timestamp from 8 feb. 2000 to 9 feb. 2000 I do: 1) User>Properties
2) Choose Timestamps
3) Check Star/End date
4) and write 00.02.08 and 00.02.09

THEN BUSINESS OBJECTS SAID THAT START DATE IS OLDER THAN END DATE.

when
4) I write 08.02.00 and 09.02.00
IT REFUSE LAST TWO NUMBER LEAVE AS 00.

  1. So what I did wrong?
    and
  2. can be here some troubles with date format?

Listserv Archives (BOB member since 2002-06-25)

2

Hi,

The format should be mm/dd/yy
If you still having problem, you can still use the up and down button to set your date one at the time mm, dd and yy

Hamid

Listserv Archives (BOB member since 2002-06-25)

3

Regional format must be set to use four digit years, bo will not work right with YY in many cases…

Found that out when my docagent went offline because end/expire date was earlier than start…

Good luck,
Brent

Date format i regional setings are - yy.mm.dd . So when I want create
timestamp from 8 feb. 2000 to 9 feb. 2000 I do: 1) User>Properties
2) Choose Timestamps
3) Check Star/End date
4) and write 00.02.08 and 00.02.09

THEN BUSINESS OBJECTS SAID THAT START DATE IS OLDER THAN END DATE.

when
4) I write 08.02.00 and 09.02.00
IT REFUSE LAST TWO NUMBER LEAVE AS 00.

  1. So what I did wrong?
    and
  2. can be here some troubles with date format?

Listserv Archives (BOB member since 2002-06-25)

4

And as long as we are on dates, I want to reiterate that you MUST set the NLS_DATE format in Oracle, if that is your back end, to DD-MM-RR, not DD-MM-YY…

Just have to put that out there, I found BO would not refresh universes correctly when that was not set.

Brent

Also, if you use mm/dd/yy in regional settings (not in bo, but windows / nt) go to mm/dd/yyyy - I thought that was a hoax, but BO recommends it, and I found that it will cause problems…

The format should be mm/dd/yy

Listserv Archives (BOB member since 2002-06-25)