event procedure not fired 1

[spikebears]

I have an access 2000 program that does not work properly in some PCs (but do work well in some machines). I got the following error message:
The Expression After Update you entered as the event property setting produced the following error:
A problem occurred while Microsoft Access was communicating with the OLE server or ActiveX Control.
* The expression may not result in the name of a macro, the name of a user-defined function, or [Event Procedure],
* There may have been an error evaluating the function, event, or macro.

The event is the [Event Procedure] for a command button click.

Thank you very much!!

 

[annsolomon]

I had this problem before. This error occurs frequently when Norton AntiVirus 2000 or 2001 is installed on the computer.

For Norton AntiVirus 2000:

Start, Run, then type regsvr32 /u "c:\program files\norton antivirus\officeav.dll" (or the path where this dll file is located).

For Norton AntiVirus 2001:

Disable Script Blocking Ann

 

[spikebears]

Thanks for your help!
Those machines do not have Norton AntiVirus installed but the McAfee. I don't think McAfee includes the script blocking funtionality. Any other suggestions?

 

[annsolomon]

Check the PCs where it does not work to make sure they aren't missing some library references. Ann

 

[spikebears]

Thanks again! I checked this issue also. The reference is Microsoft Access 9.0 Object Library and is already installed.

 

[annsolomon]

If no references are listed as missing you might try refreshing the references. (Select any library that's not already referenced then click Ok. Open references again and deselect the one you just selected. Click OK. Compile all modules.)

It's also possible that a referenced library is in a different location on some PCs. You may need to reregister it/them. Ann

 

[spikebears]

I see! Thank you! I try this and will let you know my results.

 

[spikebears]

tried! but still getting same error message.

 

[annsolomon]

Have you checked the regional settings (in Control Panel) to see if there are differences between machines that run the db okay and those that don't?

This possibility is a bit far fetched since your db does well on some PCs but I'd check it out anyway if the regional settings doesn't correct the problem. Make sure that you don't have two procedures with the same name in your code. I've accidentally done that before. Ann

 

[spikebears]

Thanks Ann, it works after I change the default system locale. Thanks again for saving a person from hell!!

Spikebears