UCase not recognized

[Alan Z. Scharf]

Hi,

I have used Ucase in several reports in an Access 2003 ADP with SQLServer.

Example: =UCase([FundName])

All reports work fine on my system. However, on clients Access 2003 system,
some reports give message "Ucase nt a valid column" when try to open report,
and on other reports I just get a #Name? in the field when the report opens.

I know it is properly finding the FundName column, because if I place a
separate FundName field on the report without Ucase, it shows up properly.

Any idea why a particular installation would have trouble with UCase?

Thanks.

Alan

 

[fredg]

Hi,

I have used Ucase in several reports in an Access 2003 ADP with SQLServer.

Example: =UCase([FundName])

All reports work fine on my system. However, on clients Access 2003 system,
some reports give message "Ucase nt a valid column" when try to open report,
and on other reports I just get a #Name? in the field when the report opens.

I know it is properly finding the FundName column, because if I place a
separate FundName field on the report without Ucase, it shows up properly.

Any idea why a particular installation would have trouble with UCase?

Thanks.

Alan

That PC has a missing reference.
Open any module in Design view (or click Ctrl + G).
On the Tools menu, click References.
Click to clear the check box for the type library or object library
marked as "Missing:."

An alternative to removing the reference is to restore the referenced
file to the path specified in the References dialog box. If the
referenced file is in a new location, clear the "Missing:" reference
and create a new reference to the file in its new folder.

See Microsoft KnowledgeBase articles:
283115 'ACC2002: References That You Must Set When You Work with
Microsoft Access'
Or for Access 97:
175484 'References to Set When Working With Microsoft Access' for
the correct ones needed,
and
160870 'VBA Functions Break in Database with Missing References' for
how to reset a missing one.

For even more information, see
http://www.accessmvp.com/djsteele/AccessReferenceErrors.html

 

[Alan Z. Scharf]

Fred,

Thanks very much.

Nothing was missing, but adding Office 11 components to list fixed it.

Not sure why. It isn't needed on my other systems. The VBA reference was
already there on problem machine.

Alan

Hi,

I have used Ucase in several reports in an Access 2003 ADP with SQLServer.

Example: =UCase([FundName])

All reports work fine on my system. However, on clients Access 2003 system,
some reports give message "Ucase nt a valid column" when try to open report,
and on other reports I just get a #Name? in the field when the report opens.

I know it is properly finding the FundName column, because if I place a
separate FundName field on the report without Ucase, it shows up properly.

Any idea why a particular installation would have trouble with UCase?

Thanks.

Alan

That PC has a missing reference.
Open any module in Design view (or click Ctrl + G).
On the Tools menu, click References.
Click to clear the check box for the type library or object library
marked as "Missing:."

An alternative to removing the reference is to restore the referenced
file to the path specified in the References dialog box. If the
referenced file is in a new location, clear the "Missing:" reference
and create a new reference to the file in its new folder.

See Microsoft KnowledgeBase articles:
283115 'ACC2002: References That You Must Set When You Work with
Microsoft Access'
Or for Access 97:
175484 'References to Set When Working With Microsoft Access' for
the correct ones needed,
and
160870 'VBA Functions Break in Database with Missing References' for
how to reset a missing one.

For even more information, see
http://www.accessmvp.com/djsteele/AccessReferenceErrors.html