Unwanted case sensitivity

[#1]

I have a database of students who have been created in a number of different academic institutions. For a variety of reasons with which I won't bore you, some of them have been duplicated across different institutions. I am trying to identify the duplicates.
My query result objects are StudentNumber, Surname, DOB, Forenames, Institution

I run the query and build the report using firstly Surname and DOB. I have created a variable Var StudentNumber which is =Count([Query 1].[StudentNumber]). StudentNumber is a unique value in the database.

When I add the variable to the report, as an example it shows:
SURNAME DOB Var StudentNumber

SMITH 01/01/2001 3

A front end search of the database shows 3 records for students with that Surname and DOB. It also shows that in 2 of the 3 records, the Forenames are recorded as John Paul, and in 1 instance as JOHN PAUL. I am satisfied that these 3 records are the same person.

When I add the object Forenames to the report, the count – Var StudentNumber drops to 2 and the record with the Forenames in UPPERCASE is not returned.

I do not understand why, or where, this case-sensitivity is being applied or how to switch it off or overcome it in some other way.

I do NOT have access to the ‘write your own SQL’ functionality. I can only create variables.

Any help, advice, thoughts would be much appreciated.

[ayman_salem]

It appears that you have merged two queries using the First Names dimension. and one query is UPPER CASE and the other is not.

So if you have merged the query, then merged with the id (if available).

[former_member1189195]

Thank you for taking the time to reply. Unfortunately I don't at the moment understand what you are saying. There are not two queries; there is only one query with 5 Result Objects and a Variable. I have not merged two queries.

I don't understand what this means either: "So if you have merged the query, then merged with the id (if available)"