OLD version problems

[Chris_(Guest)]

Hello, __Maybe someone can help with this problem__I have recently upgraded a system from R&R v5 to R&R v6.__The problem is that when I run custom reports they ignore the date range inputted by the user and run the report for all data in the system.__I know this is a few years out of date but hopefully one of you may have used the system back then!!__Thanks in advance__Chris

[kfleming]

How are you passing the date range to the runtime report?__Do you see the same problem when you open the report in RR.EXE?____There is nothing that changed between V5 and V6 that should cause this specific behavior.____Kathleen__R&R Support

[Chris_Strasser_(Guest)]

Are you using version 6 for windows? I used that quite extensively for some time and noticed that dates in {} didn^t always work properly in the report. I wound up using CTOD() in calculations and specifying a plain-text date in all applications.

[Dave_Francis_(Guest)]

Don^t forget the 2000 problem with most old RR versions - always force the user to enter the full century. __BTW - I still have date calculations that fail in 8.1, sometimes depending on the date value.

[kfleming]

Using the shortcut of entering only 2 digits for a 4 digit year has been a bad idea all along. We originally allowed it since dBase allowed it. We should have been smarter (like we are now!)____But back in those days, the year 2000 seems like such a long way in the future.____Kathleen __R&R Support

[Chris_Strasser_(Guest)]

I^m interested in finding out what date calcs fail for you in 8.1. Can you post your findings here for review? Thanks!