Help - some of our users have a problem with Date LOVs that they didn’t have before. The AM indicator appears twice in the list (eg. 7/1/1999 12:00:00 AMAM)and when this is used in the query the generated SQL will not work. Have confirmed that it’s not a database problem. When the date field is included in a report and formatted to display full date time stamp it’s OK. So I think it’s a display/format issue within the LOV display. Has anyone else experience this? Could it be an ODBC issue? I’m trying to track down what has changed on the workstations that have this problem. Thank you for your replies.
I noticed this problem alongside other problems in WEBI 2.0.1 I’ve now installed WEBI 2.0.7, the date/time formats seem to be OK.
Hope this helps (or not).
Minal
Help - some of our users have a problem with Date LOVs that they didn’t have
before. The AM indicator appears twice in the list (eg. 7/1/1999 12:00:00
AMAM)and when this is used in the query the generated SQL will not work.
Have confirmed that it’s not a database problem. When the date field is
included in a report and formatted to display full date time stamp it’s OK.
So I think it’s a display/format issue within the LOV display. Has anyone
else experience this? Could it be an ODBC issue? I’m trying to track down
what has changed on the workstations that have this problem. Thank you for
your replies.
I have seen this problem sporadically using 4.1.1. It also impacts the “Last Exec:” date display at the bottom of the screen. I believeBusObj support said it was fixed in 4.1.5.
As a workaround, we tell users to delete the extra AM or PM after selecting a date from the LOV.
We too have experienced this problem using BusObj 4.1.1. The resolution we have offered our users is to go into Start >> Settings >> Control Panel >> Regional Settings >> Time tab and set the time style to “h:mm:ss”. Most of our users had “h:mm:ss:tt” and by removing the “tt” this solved the problem (although the clock in the lower right corner will no longer show AM/PM). BusinessObjects Tech Support suggested setting the time style to military time; this also works.
We are not 100% sure what has caused the problem, but we believe it has something to do with the combination of Windows NT, BusinessObjects 4.1.1, and Microsoft Outlook.
Hope that helps.
Caren Katz
Hartford Investment Management Company
Investment Systems
Hartford, CT caren.katz@thehartford.com
Original Message:
Help - some of our users have a problem with Date LOVs that they didn’t have before. The AM indicator appears twice in the list (eg. 7/1/1999 12:00:00 AMAM)and when this is used in the query the generated SQL will not work.