Simple Brio problem

[mark]

So simple that I can't sort it!

Have a report that is stripping the HH, MM and SS from a computed column.
The computed column is fine, the HH and SS is fine, however, the MM (minutes) column has developed an issue.

If I process the report prior to the 3rd Feb, the results are 2 digits (all under 60 of course), post 3rd Feb, the column return 2 digits and 5 decimal places.

I've tried to change the way the number is displayed but it doesn't change.

Knock on effect is another column (with date and total time in HH:MM:SS) looks completely wrong!

Any suggestions?

Cheers Mark
(been away a while I know!!)

[tony]

Hi Mark - nice to hear from you again - welcome back!

[list]
[li]Right-Click and check the Format of the column - Is it a standard format, or a custom one..?  Can you change it..?[/li]
[li]Have any of your CCA components been upgraded recently?  That includes SQL/Oracle...[/li]
[li]Could you strip out the report and put a copy of the .bqy file on here...?  Obviously remove the results, aside from 2 comparison dates and I can have a quick look...[/li]
[/list]

Tony

[mark]

Morning Tony

Nothing has changed in terms of components that we are aware of (I only started Monday, so something may have happened that hasn't been logged and that nobody wants to admit to).


Just ran the report again, this time it has processed correctly for all days since the 5th (yesterday it was erroring on all days from the 3rd)!!
One of those very odd things I think.

Unable to get the .bqy file as I have to connect to a specific box (via remote desktop) and unable to map directly to the drive which holds the files from my own desktop :/

[tony]

Corrupt data in the table...?

Weird!

Tony

[mark]

Oddly the data that its using to compute is fine, its purely the result that shows incorrectly.

Very odd. I'm going to blame this on Canada.

[tony]

Timezone/Time Settings on the Server/Desktop....

OK - I'm clutching at straws... I'll stop now... lol

Tony

[Cuore_2003]

Can you extract in a column only the seconds of the incorrect column?

I mean:
- First column extract HH
- Second column MM (or in first column, HH and MM are corrects)
- Third column SS

If SS data are incorrect displayed perhaps you can set the correct format and set a new column with HH MM SS.
That’s not a solution but, perhaps you could solve the incident.

[mark]

[quote author=Cuore_2003 link=topic=3831.msg16653#msg16653 date=1234430357]
Can you extract in a column only the seconds of the incorrect column?

I mean:
- First column extract HH
- Second column MM (or in first column, HH and MM are corrects)
- Third column SS

If SS data are incorrect displayed perhaps you can set the correct format and set a new column with HH MM SS.
That’s not a solution but, perhaps you could solve the incident.

[/quote]

HH, MM and SS are already extracted separately, for a couple of days only, the MM was giving an incorrect format. Its ok for now though, which makes it quite odd!

[tony]

MM is sometimes translated as "MONTH".  Isn't it NN for seconds...?

[mark]

[quote author=Tony Tillyer link=topic=3831.msg16721#msg16721 date=1234537797]
MM is sometimes translated as "MONTH".  Isn't it NN for seconds...?
[/quote]

Possibly, what we have is the HH being broken down into mins by the calculation:

if (Math.floor((T_Inbound_Talk - (Total_Inbound_Talk_Time_HH * 3600)) / 60) < 10)  {
        "0" + Math.floor((T_Inbound_Talk - (Total_Inbound_Talk_Time_HH * 3600)) / 60)
}
else    {
        Rtrim(Math.floor((T_Inbound_Talk - (Total_Inbound_Talk_Time_HH * 3600)) / 60), '.')
}

then the column for it is just named MM etc

[tony]

My eyes aren't what they used to be but isn't this saying; if it's under 10 seconds, mark it as zero seconds - otherwise return the number of seconds...?

[mark]

To me it looks like its saying if its less than 10, apend a 0, so that it keeps it at 2 digits.