Problem with UCase

[Bill Perry]

I'm having a problem with UCase! Any ideas?

Why, in Access 2010, does "=UCase([FieldName])" placed in a report text box record source, return "#Type!" in report view instead of the text in that field from my query FieldName?

Thanks,
Bill

 

[pr2-eugin]

Does the FieldName actually have values in them? No Date or number types?

 

[GohDiamond]

I've tried to produce the #TYPE! error as you've said. The UCase() function requires a STRING. Only once when I defined the field using the [TABLENAME]![FIELDNAME] did it produce the error which lead me to believe that it did not see that as an available string eventhough the TABLENAME was the table from which all the fieldnames are provided.

When I simply used any fieldname in the fieldname list like ucase([AnyFieldNameInMyList]) it never failed to change any Alpha-Numeric characters to ALPHA-Numeric

Try using it in another report and see if it works. if it does there may be some corruption in your Report or the Fieldname value is not being recognized. Could it be null?

Cheers!
Goh

 

[Bill Perry]

Thanks for your reply!
I am reporting on a query that is getting data from two tables! Both UCase() & StrConv() work on fields from the main table but not on the linked table? And, yes there are text values in the fields I am reporting on. In the report Data Control Source I have tried naming both the query and the field and just the field alone but keep getting the message of “#Type!” when I use the field from the linked table.
Any ideas?
Bill

 

[GohDiamond]

What is the linked table source? Another Access DB? Excel? Oracle? SQL Server?
Goh

 

[Bill Perry]

Hi Goh, Both tables supplying information to my query are Access 2010 in the same DB. Bill