By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
426,107 Members | 1,284 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 426,107 IT Pros & Developers. It's quick & easy.

Unrecognised command in Win2000 but not in Win98

P: n/a
My access 2000 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

Nov 12 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
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
"Steve" <st***@nomorespam.tolleyonline.net> wrote in message
news:d4******************@newsfep4-glfd.server.ntli.net...
My access 2000 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

Nov 12 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.