Format$ function doesn't work after migrating to 2003 SP2

[Guest]

After developing a database using Access 2000, and getting a new PC with 2003
installed, any report using the Format$ function now pops-up an "enter
parameter value" window instead of recognizing the table date field (which is
defined as a long integer.)

Creating a new report using the original table data doesn't work either.

Creating a new report with a new table works.

This doesn't work when 2003 knows it's a 2000 database, nor after I've
converted it to a 2002-2003 database.

Have looked through Microsoft for any problems, but can't find anything.

Any suggestions? Thanks!

 

[fredg]

After developing a database using Access 2000, and getting a new PC with 2003
installed, any report using the Format$ function now pops-up an "enter
parameter value" window instead of recognizing the table date field (which is
defined as a long integer.)

Creating a new report using the original table data doesn't work either.

Creating a new report with a new table works.

This doesn't work when 2003 knows it's a 2000 database, nor after I've
converted it to a 2002-2003 database.

Have looked through Microsoft for any problems, but can't find anything.

Any suggestions? Thanks!

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

 

[Guest]

fredg:

Thanks for your quick response to my questions. It took a couple of tries
to get the box unchecked, but it did clear up the problem.

I haven't yet looked at the Knowledge Base articles you referenced, nor the
link to the article, but will do it to more fully understand what the problem
was.

Thanks again,

Craig