MySQL Time fields display as "0:00" 1

[JCruz063]

Hi All,

I had the Crystal Reports version .NET version (the one that ships with Visual Studio .NET 2002), and I bought an upgrade for version 10. One of my reports connects to a MySQL server which has a table that contains a "Time" field. In the report, the time field is being displayed as "0:00" all the time.

The Crystal Reports site mentions that this is a known problem with Crystal Reports version 9, and that it is fixed in the appropriate Service Pack for version 9. Now, I have version 10 (which was an upgrade from the .NET version) and I have the problem. Does anyone know how I could fix it?

Thanks!

JC

_________________________________________________
To get the best response to a question, read faq222-2244.

 

[synapsevampire]

Which driver are you using?

Nore the whitepaper makes reference to this "If a report is created using the MySQL 2.50 database driver, all time fields display as 6:04PM. If a report is created using the MySQL 3.51 database driver"

I'd try the latest driver.

Just in case, you might also apply the Crystal 10 service pack:

http://support.businessobjects.com/fix/hot/si75/default.asp

-k

 

[JCruz063]

Thanks synapse,
I'm not sure which driver I'm using... I thought Crystal Reports version 10 used the same driver as any other version 10. I'll try to look it up.

As for the version 10 Service Pack, I applied it already, but I still get the same problem.

Thanks!

JC

_________________________________________________
To get the best response to a question, read faq222-2244.

 

[synapsevampire]

I believe that the driver is supplied by MySQL, not Crystal.

You should be able to d/l the latest at their site.

-k

 

[JCruz063]

Thanks again!

I already have the very lastest drivers from MySQL. I believe the problem lies on the Crystal Reports side.

The Crystal Reports site says their version 9 Service Pack fixes this problem. Given that I have version 10, I should have all bug fixes pertaining to version 9 already installed in my machine. However, I still have the problem.

I'm guessing that perhpas version 10 was released before the version 9 Service Pack came out and thus my version doesn't have the fix included. At the same time, the version 10 Service Pack that I installed seems not to address the issue and so I'm stuck with the problem. Does this make sense? If so, what can I do to fix it?

Thanks!

JC

_________________________________________________
To get the best response to a question, read faq222-2244.

 

[JCruz063]

hmmmm, I was just wondering... is it ok to apply a version 9 service pack to a machine running Crystal Reports version 10?

Thanks!

JC

_________________________________________________
To get the best response to a question, read faq222-2244.

 

[synapsevampire]

Not a good idea...

-k

 

[JCruz063]

Any clue why I'm still getting all time fields as 12:00:00 PM ?

JC

_________________________________________________
To get the best response to a question, read faq222-2244.

 

[synapsevampire]

I'm somewhat stumped here, I'd think that they'd resolved it.

You're definitely refreshing the data, right?

You might use a CAST or CONVERT statement in a Crystal SQL Expression and cast it to a varchar and then in Crystal you can convert it back.

That should resolve it.

-k

 

[JCruz063]

I am refreshing the data...

How would you go about CASTING it?

Thanks!

JC

_________________________________________________
To get the best response to a question, read faq222-2244.

 

[synapsevampire]

I don't us MYSQL, so you'll have to look up the syntax.

Try the following syntax:

Cast(table.field as varchar)

-k

 

[JCruz063]

Thanks synapse,
For the time being, I just changed the database field itself to varchar. It's working fine. Later on, I'll get to the bottom of it. For now, though, it's a varchar field!

JC

_________________________________________________
To get the best response to a question, read faq222-2244.

 

[JCruz063]

Just so that you know... I contacted Crystal Reports and they told me that's a known issue with version 10 (that was, of course after telling me to try a few things).

According to them, the fix isn't out yet but they're working on it. There is a fix for the same problem for version 9, but the problem exists as well in version 10 and they haven't fixed it yet (interesting, don't u think?).

Thanks for your help!

JC

_________________________________________________
To get the best response to a question, read faq222-2244.