Upgrading to LBI 10

I can modify your report... but that wouldn't really get you anywhere. Sounds like you are on a track following Matt's advice and suggestions.
If you'd like me to, I'd still be happy to publish your rpt file here... but as I said, it would have to be modified slightly.

Is your SQL Server set up with a collation of Case Sensitive? not sure why RS is changing it but you could try using the UPPER function in your where clause if is as an immediate remedy.

Greg,
We have several issues with our reports in LBI 10.1. The SQL being modified is just one of them.
I have attached the report here and I would appreciate it very much if you could test run it.
Ric

By the way Greg,
Run it with Company, Year Range and Period range only.
Leave the other parameters blank.
Thanks.

Matt, It doesnt really make any sense to hardcode UPPER a hardcoded string of "AC". but I tried it and it worked!
Im working on the other issues though.

Some findings. We apparently do not have a ACACTIVITY.USR_STATUS='AC' OR ACACTIVITY.USR_STATUS='CL', but when I put valid values in from our table, it runs in Crystal 2008. However, I cannot get it to run in LBI. It keeps prompting me for values, but when I enter them and click 'Run' it comes back with a message dialog box saying that parPeriod1: Data entered is greater than the allowed maximum for this parameter. I've gone in and taken the max value you had set (12) off and replaced it with nothing. Still no go. Same symptoms happen for parPeriod2.

rick, I agree it doesnt make any sense but i think the explanation is RS constructs SELECT clause by parsing the report model and then constructing the SQL to be executed. Some where between the Crystal SDK and RAS the values are getting their case changed. Normally this wouldnt matter unless you have a database with a case sensitive collation. By using the UPPER function, it wont matter what they do to your hardcoded string because the function will run on the database not in the Crystal SDK.

Really think you need to report this to Infor but atleast youve got a work around for now.

Matt, I have reported it to Infor. Interestingly, the support person replied he knew about it already!
I would not settle for that workaround though, we have a lot of reports and modifying each just to acommodate 10.1 is not very appetizing. Thank you for all you help.

Greg. not sure what's going on there, but I appreciate you trying it. Thanks!

Rick, any update for Infor about an available/upcoming fixpack to address this issue?

We've since installed 10.2.0.160 in our test environment. I don't have any time available today... or possibly tomorrow, but if I can get them to work there, I'll report back.
*Note: The move from 10.1 to 10.2 required Crystal Reports 2011 for the RAS server... seems that older reports still run, though.

So, OK.... I took the time. I still run into the same kind of errors that I described earlier on 10.2 *Even after saving your report file in Crystal 2011.

It runs in Crystal 2011.. just doesn't return any data (for us).. but not from LBI.

Thanks Greg