Cisco Call Manager Dates in Crystal Reports
by danlor on Feb.16, 2007, under Technology, Work
Once again, I hit a wall when trying to integrate all my databases here at work. This time, I was stymied by the fact that even though Cisco CCM runs it’s database on MS SQL server, the system does not use native date/time formats. Instead it decides to use the industry standard… number of seconds since January 1st, 1970. So I have a huge long integer. No problem right? I’ll just put it through Crystal’s formula engine. Except I get an error telling me the year is out of range.
Turns out the Crystal Date functions are based upon DAYS, not seconds. and the base date is 1900, not 1970. So, in order to make this work, I need to convert our integer from seconds to days, and then offset our number by 70 years. So what’s the solution?
CDateTime ({call manager date value}/(24*60*60)+(Date (1970, 1, 1)-Date (1900, 1, 1)))
You are welcome.
March 31st, 2007 on 3:29 pm
http://yro.slashdot.org/yro/07/03/31/1725221.shtml
now that is messed up
July 3rd, 2007 on 1:09 pm
Gotta love the US Government. They know what’s best. If you don’t like it… you are a terrorist. You like it… RIGHT?
July 11th, 2008 on 10:29 am
Hi, I stumble to your website when I was searching to run report from call manger using crystal report. If you can help, I would appreciate it.
I am a network Engineer not a DB person, do you have any document or link to use to run report from call manger CDR table using crystal report?
September 28th, 2010 on 11:05 am
Thank you for the post for this! I do have an alternate solution though…
DateAdd(“s”, {Callmanagerdatevalue} – 14400, #1/1/1970 00:00:00#)
Should get you the same results 🙂