Format Date

[Guest]

Why on some computers does Format(Date(), "mm/dd/yyyy") work and others it
doesn'?. Am I missing a setting?

 

[fredg]

Why on some computers does Format(Date(), "mm/dd/yyyy") work and others it
doesn'?. Am I missing a setting?

"Doesn't work" doesn't tell us anything. What does happen?
I would guess you're getting an "Unrecognized function" error message.

If so, 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]

On my computer I am using Windows XP "Home" operating system and am currently
up to date with Service Packs. I also am using Microsoft Office 2003 with a
full installation and all the current updates. My partner is using Windows
XP "Professional" operating system. He is also up to date with Service
Packs. He is also using Microsoft Office 2003 with a full installation and
all the current updates.

Using the same Access program with the same References in the same order the
Format Date function works on my computer and it doesn't work on his. His
comes back with an "Unrecognized Format" message. Thanks for you help.

 

[Douglas J. Steele]

Did you try Fred's suggestion?

Problems with the References collection can be caused by differences in
either the location or file version of certain files between the machine
where the application was developed, and where it's being run (or the file
missing completely from the target machine). These can occur even on the
machine on which the application was developed if new software is installed.

On the machine(s) where it's not working, open any code module (or open the
Debug Window, using Ctrl-G, provided you haven't selected the "keep debug
window on top" option). 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)

For far more than you could ever want to know about this problem, check out
http://www.accessmvp.com/djsteele/AccessReferenceErrors.html, or check my
December, 2003 "Access Answers" column in Pinnacle Publication's "Smart
Access" (you can download the column, and sample database, for free at
http://www.accessmvp.com/DJSteele/SmartAccess.html)