"Function Name That Microsoft Access Can't Find

[John Skolits]

I get this message:
"Access trying to run a function name That Microsoft
Access Can't Find".

This happens when I simply call a basic function from
within Access 'using a macro'.

This is a database with one macro and one function. In the
first line of the macro, I call the 'MsgBox' routine.

In the second line I call MSGBOX using 'RunCode' with a
custom function. When I execute the macro, the first line
works, the second fails.

I can use the function call from the Immediate window with
no problem.

How It Started:
The user was half way re-loading WIN XP on his PC when he
cancelled the
process. XP was already on it so there was no need for him
to run the setup.
Once he realized it he cancelled it. Now Access won't work
correctly.

Already Ran MDAC 2.8 and reinstalled Access. This is an
Office XP machine.
Any ideas?

John Skolits

 

[Wayne Morgan]

If he was in the process of reloading WinXP and cancelled, there is no telling what may be
wrong? Does the database work on other computers? Have you run a repair install on WinXP
then reapplied the Windows patches? I suggest that you try one of the WinXP forums first
for more information on this.

While this doesn't sound like the problem, it may be worth while checking this.
http://members.rogers.com/douglas.j.steele/AccessReferenceErrors.html

 

[John Skolits]

I was having problems with my custom database, so I
decided to create a brand new one with the functions I
told you about. So it's not a DB design issue.

There are also no references beside the default ones and
none are missing.

 

[Wayne Morgan]

Does it work on any computer? Which functions aren't working?

 

[John Skolist]

Here is the function:


Function MsgBox_Fuc()

MsgBox "Testing Message 123"

Exit function

That's it. It the only thing in the database. No tables,
no queries, no nothin'. And works on all other PC's. I'm
sure what happened is some Windows dll is corrupt or
something.

 

[Van T. Dinh]

I ran similar code without any problem so I am fairly sure it is in the
user's OS and/or Office set-up.

Suggest using the "restore to original installation" (???) option for BOTH
WinXP and Office.