Crystal cannot find a match between the lower case and upper case versions of the UserID, so should I just tell the customer that they cannot link those two tables any longer or are you aware of any fix in the works?

John, we have SP9 installed. Are you saying the userID field in the SkillsetbyAgent table should be lowercase? It's uppercase in our system.

I've come across a problem where a customer's custom Crystal reports work when run for a period prior to their recent upgrade from CC7 to AACC6.3 (SP9), but the reports don't work when run for a period after the upgrade.

The report uses a link from the SkillsetbyAgent table to the dAgentPerformanceStat table to select data for agents who have particular skillsets assigned. The link between the two tables is by UserID.

Upon digging, I can see that the capitalization of the UserID field changed during the upgrade. If I look at the UserID field in dAgentPerformanceStat, the letters are uppercase prior to the upgrade, but lowercase after the upgrade. The SkillsetbyAgent table is all uppercase.

My suspicion is that the join is not working because it won't find a match between the uppercase UserID in the SkillsetbyAgent table and the dAgentPerformanceStat table.

Anybody come across this yet? Am I barking up the wrong tree? Do you think Crystal should establish a match regardless of case?

Paul, did you get your problem worked out? I'm having the same problem, so I'm curious to hear if you found a resolution.

Hi John! In my case, yes, we were using the new 6.3 version of the SDK. I'm going to try Kenneth's workaround and see if that works for us.

Has anyone found a solution to this issue? I have seen it on two separate customer sites. We've noted that it only occurs when using Internet Explorer. It does not occur when using Firefox or Chrome.

Hi John, is there already documentation on what's new with this new SDK that will be released? Or do we need to wait until it is released? I'm trying to decide whether to advise my customer to wait for it or to proceed with the 6.3 SDK.

Thank you, John. Can you also confirm that SDK 6.3 or even the new SDK will NOT work with AACC 6.2? Will the new SDK be released at the same time as AACC 6.4?