Time Formula Doesn't Work in version 9.0

[jonesanne]

I have a formula that shows meeting times.

If IsNull{@hour} Then ""
Else ToText({@hour},"hh:mm&quot

In v.7 the output was 10:00 or 12:00, etc.

We recently upgraded to v.9 and some of the output is now 9:59 or 11:59, etc. (Some are still showing the correct times).

Is there an easy way to correct this?

Thanks!
Anne

 

[MJRBIM]

The meeting times formula contains another fomula called {@hour} - please post the contents of that formula.

 

[jonesanne]

Yes, {@hour} converts the date/time field into a Time field:

Time({CONSOLIDATEDCALENDAR.TIME})

I did check the database to make sure the time was entered correctly. Like I mentioned, this problem didn't come up until we started running the report in V.9. It works well in V.7.

Thanks.

 

[Ngolem]

Why do you have to convert the date/time value to a time value?

eliminate the formula

If IsNull({CONSOLIDATEDCALENDAR.TIME})Then ""
Else ToText({CONSOLIDATEDCALENDAR.TIME},"hh:mm&quot

Does that make a difference?

Jim Broadbent

The quality of the answer is directly proportional to the quality of the problem statement!

 

[jonesanne]

I had to create {@hour}in v.7 because the date/time field output was both date and time & I only wanted to see the time.

I tried your formula, which definately makes more sense than what I had, but the time problem still wasn't resolved.

I ran the report in v.7 just to make sure I'm not losing it, but the time shows just perfectly in that version.

 

[jonesanne]

Another note: When I browse the data in that field, Crystal shows it as 9:59, 11:59 and so on (not for all records, though). Could this be an MS Access/Crystal v.9 problem?

 

[synapsevampire]

Assuming that the time in the Access table does reflect 12:00, and not 11:59.

It could be a connectivity issue, try changing the connectivity type from Native to ODBC, or vice versa.

Also apply the monthly hotfixes.

-k

 

[jonesanne]

You're going to have to help me on the connectivity solution. How would I do that?

I downloaded the Oct. hotfixes this morning, hoping that it would solve the problem. No deal.