Unrecognised command in Win2000 but not in Win98

[Steve]

My access project was written on a win 98 machine and has a macro with a
condition

DateValue(FileDateTime("c:\database\full22.txt"))<Date()

This was written in expression builder.

On the Win 98 machine all works fine. When using same datbase on a Win 2000
machine this
condition fails and generates message "unrecognised function........."

It appears to be the filedatetime section that is not working. In the
immediate pane of the VB code section of access on the win2000
machine the expression works fine. It seems to just be a problem when used
as a macro condition.

Has anyone got any ideas how to resolve the problem

Many Thanks

SteveT

 

[steve]

Correction to my previous post. The actual error message is "The expression
you entered has a function name that db4 can't find"
Access version is 2000.

Any clues??

steve

 

[Douglas J. Steele]

Your references are probably messed up.

This 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). Such differences are common when 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://members.rogers.com/douglas.j.steele/AccessReferenceErrors.html