Crystal Report dates

Hi, Our software is RMS and we have Crystal Reports (brand new). We're trying to run a report but the date fields are screwing us up. Help!

Reply to
Jan
Loading thread data ...

Jan, I don't have much to go on with your post, but RMS is very particular to the version of Crystal Reports that it runs internally. CR 8.5 is the default version that *should* work with RMS. Some have said that even then, the def files sometimes need a little tweaking. I, have 8.5 Dev and 11 (XI) Dev, and have used both in different methods,

11 as an externally called VB routine.

What do you mean by "screwing us" up? Do you mean that the data isn't accurate, the date fields aren't formatting properly, etc...? A litle more info or a reference to a sample download of this report and what you are hoping to do with the report versus what it does would help everyone out. There have been a lot of people kind enough to give me their insight and advice, provided I adequately described what I had and hoped to accomplish.

Write back at your c> Hi,

Reply to
Fisher

Hi Kevin,

You're right about giving more information. I hope this little description is enough as I'm not real versed in computer-ese and am self teaching a lot of the software associated with RMS. The Crystal reports software was just purchased and it is Crystal Reports XI.

The person trying to create the reports said the date has to be in a certain format, say mm/dd/yyyy and has been trying all different combinations of possibilities i.e. mm/yyyy, mm/dd/yy, m/d/yy, etc. Then try to run the report and nothing comes up. So, I'm not sure what's happening but hope this bit of info helps.

Jan

Reply to
Jan

Well, I'm still not sure exactly what you're trying to do, but this may help... The dates in RMS are DateTime, so for example if you try "WHERE [Transaction.TransactionTime] = '7/5/2005'" you may not get any matches, but if you use "WHERE [Transaction].TransactionTime BETWEEN '7/5/2005 00:00:00' AND '7/5/2005 23:59:59'" you probably will. I don't use Crystal, so I don't know if this is your problem or not, but it's worth a try. Generally, SQL Server will try to decipher any date format - 2005-07-05, 07/05/2005,

7/5/2005, 7/5/05 will all work - your Windows Date format settings may also come into play.

Hope that helps, Glenn

Reply to
Glenn Adams [MVP - Retail Mgmt]

BeanSmart website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.