Input/Output functions can't be found.

[Mike]

Microsoft Access produces the following error message when
I run a macro containing one of the Built-in Input/Output
functions (i.e. Dir, FileDateTime, etc.):

"The expression you entered has a function name that
Microsoft Access can't find."

For example: Within the "Condition" field of a macro I
have Dir("C:\"). I am running Windows 2000 and Access
XP/2002 (Office XP/2002). The same error occurs when I use
Access 2000.

All other Built-in functions work fine. How do I get
Microsoft Access to find its Built-in Input/Output
functions?

 

[John Vinson]

Microsoft Access produces the following error message when
I run a macro containing one of the Built-in Input/Output
functions (i.e. Dir, FileDateTime, etc.):

"The expression you entered has a function name that
Microsoft Access can't find."

This appears to be the very common References bug. Open any
module in design view, or open the VBA editor by typing
Ctrl-G. Select Tools... References from the menu. One of the
..DLL files required by Access will probably be marked
MISSING. Uncheck it, recheck it, close and open Access.

If none are MISSING, check any reference; close and open
Access; then uncheck it again. This will force Access to
relink the libraries.

 

[Guest]

Thanks but this didn't work. I found no dll's marked as
MISSING but I did check a reference, restart Access and
uncheck the reference, but still no luck.

Could the fact that only the Input/Output Built-in
functions and not any of the other built-in functions be a
clue?

Mike

 

[John Vinson]

Thanks but this didn't work. I found no dll's marked as
MISSING but I did check a reference, restart Access and
uncheck the reference, but still no luck.

Could the fact that only the Input/Output Built-in
functions and not any of the other built-in functions be a
clue?

Could be, but I'm baffled. I don't know what library might be messed
up to cause this - I'd suggest you repost so some other volunteers
with more experience could pick up the thread!

 

[Mike]

Thank you!
Mike

-----Original Message-----


Could be, but I'm baffled. I don't know what library might be messed
up to cause this - I'd suggest you repost so some other volunteers
with more experience could pick up the thread!



.

 

[John Vinson]

For example: Within the "Condition" field of a macro I
have Dir("C:\"). I am running Windows 2000 and Access
XP/2002 (Office XP/2002). The same error occurs when I use
Access 2000.

Another MVP, John Spencer, whom I asked about this reports:

I tested this under Access 2000 and Windows NT and I didn't run into a
problem.

Macro Condition: Dir("C:\")<>"" (Variant Dir("C:\")="")
Macro Action: OpenForm
Action Arguments: frmAddQuestions (a valid form)

With the not equal the form opened. With the Equal the form did not
open.

I also tried just Dir("C:\") as the condition. Interestingly enough,
it opened the form and when I tried a non-existent directory, the form
also opened.

 

[Mike]

Please note that Rob Cooper resolved this issue - see his
response to the Oct. 30 2003 8:48AM posting with the
subject line of: "function name Access can't find".

The essence of the resolution is:
Change HKEY_LOCAL_MACHINE\Software\Microsoft\Jet\4.0
\Engines\SandBoxMode from 3 to 2.

Thanks for all the help!
Mike