Access 97 Function calls from events stop working.

[barnstorm]

Hi Folks

I have a very odd one

I have an Access 97 MDB application. It has all been working fine for over a year - upwards of 10 users.
Suddenly one user starts getting errors.
On investigating I find that event procedures and calls from code are working fine.
What is not working is calls to functions directly from events. They give the "Bloggs.MDB can't find the Macro or Function blah blah blah" as if the name was misspelt. (It is not !) Every other user is working fine. I have got a fresh copy of the mdb. I have recompiled the modules the database on the machine in question.
Then I notice his Access is SP1 - Putting on SP2 fixes everything - he is fine - it all works - until he restarted next morning when the problem came back.
I have tried a noddy database written from scratch on his system and it shows the same faults - seems like it is Access that has the problem not the MDB.
If it is relevant he is using Windows ME - everyone else has Windows 98 I think.

HELP PLEASE!!!

Ian J

 

[bjd4jc]

Do you have any COM objects that are missing? I've seen this before when I had a missing reference... not absolutely sure this is your prob but it is worth a shot.

 

[CCLINT]

Are they user defined functions and if so then where are the functions located? Do the SAME functions work outside of event proceedures? (try calling these from the Test window). It may be only a matter of calling the function differently (instead of MyFunction() using Module1.MyFunction() )

If they are Access/VBA functions, are the work stations where they are not working all updated to service pack 2?

Are the functions used in an SQL SELECT statement? If so, do all machines have updates to MDAC 2.5 and Jet3 sp3 (DAO/Jet) or MDAC 2.6/7 Jet 4 (ADO/Jet)? And if so, what are the functions?

 

[barnstorm]

Thanx everyone for the feedback

CCLINT - The problem originally occurred in an mde library
However in my noddy database I tried the function in a library, in a module, and in the form's own code. none worked - just event procedures.

The function is exceptionally simple and does not use SQL.
It does not seem to matter what is in it
In my noddy test the function was simply DoCmd.Close !!

Problem only on one user who was on SP1 and working fine for many months prior - Installing SP2 cured it but it recurred.

All database access in the database is by DAO 3.51 - ADO is never used. Don't think MDAC 2.5 and up is relevant (???)

I am not regularly on the site.
Currently I am being told of a virus problem occurring at the same time as the problem, and am waiting for more information on this. Will post more info when I get it.

 

[barnstorm]

Hello to everyone who has replied
The company that maintains the installation (nothing to do with me) has gone through a virus removal procedure on this PC and detected FOUR different viruses on the system.
On cleaning it the problem has gone away.

Sorry to waste everyone's time - but we all now know that an effect like this can be created by a virus. This surprised me at least !!!