Format function doesn't work

[Robert]

I am trying to use an Access database developed on a computer with Access
2003 on a computer with Access 2002 and I get an undefined error message on
the function Format. How can I correct this? I think it has to do with the
libray selection but I can't remember where that is.

Robert

 

[Douglas J. Steele]

Odds are there's a problem with your References collection.

Open any code module, then select Tools | References from the menu bar.
Examine all of the selected references.

If any of the selected references have "MISSING:" in front of them, unselect
them, and back out of the dialog. If you really need the reference(s) you
just unselected (you can tell by doing a Compile All Modules), go back in
and reselect them.
\
If none have "MISSING:", select an additional reference at random, back out
of the dialog, then go back in and unselect the reference you just added. If
that doesn't solve the problem, try to unselect as many of the selected
references as you can (Access may not let you unselect them all), back out
of the dialog, then go back in and reselect the references you just
unselected. (NOTE: write down what the references are before you delete
them, because they'll be in a different order when you go back in)

 

[Robert]

You are right. The problem, I think, is that this database has some Excel
automation in it. And yes, the Excel object library 11.0 is missing. For
Access 2002, I selected Excel 10.0. Excel 11.0 isn't there. It's working
so far.

No wonder I couldn't find those references, I was looking for it in the
database, not the code.

Thanks.

 

[Tony Toews [MVP]]

You are right. The problem, I think, is that this database has some Excel
automation in it. And yes, the Excel object library 11.0 is missing. For
Access 2002, I selected Excel 10.0. Excel 11.0 isn't there. It's working
so far.

Late binding means you can safely remove the reference and only have
an error when the app executes lines of code in question. Rather than
erroring out while starting up the app and not allowing the users in
the app at all. Or when hitting a mid, left or trim function call.

This also is very useful when you don't know version of the external
application will reside on the target system. Or if your organization
is in the middle of moving from one version to another.

For more information including additional text and some detailed links
see the "Late Binding in Microsoft Access" page at
http://www.granite.ab.ca/access/latebinding.htm

Tony

 

[Robert]

Will take a look at it.

Late binding means you can safely remove the reference and only have
an error when the app executes lines of code in question. Rather than
erroring out while starting up the app and not allowing the users in
the app at all. Or when hitting a mid, left or trim function call.

This also is very useful when you don't know version of the external
application will reside on the target system. Or if your organization
is in the middle of moving from one version to another.

For more information including additional text and some detailed links
see the "Late Binding in Microsoft Access" page at
http://www.granite.ab.ca/access/latebinding.htm

Tony

--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
Granite Fleet Manager http://www.granitefleet.com/