Discussion Locked

Error message with MS Access 2000

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I am currently writing developing a small database for use by my Company as a Purchasing System. I am not brilliant with VB and under advice, used some code from the examples provided with MS Access 2000 (namely the Orders db)

I have structured the database around the code however when I try to run the code I get the following error message:

"The expression On Dbl Click you entered as the property setting produced the following error. A problem occurred while Microsoft Access was communicating with the OLE server or ActiveX Control"

Seeing as this is a standard non sensical error from MS, I would really like a resolution as to
a) what does it mean and
b) how do I resolve its issues

The code is pretty standard VB code - nothing fancy, and I can provide it if necessary if that helps in resolving my problem.

5 replies

by sl-campbell

This could be caused by Norton AV. IS it installed?

I have had this and seen this many times. The answer in the MS Kb article below didn't work for me and I had to turn off NAV one time and uninstall it another time. The problem doesn't lie with MS but with NAV.

You can check out this site:
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q295824

(Remove any spaces in the URL or search the article number in the MS Kb)

by al

I initially switched off Nortons - nothing changed, and then deinstalled and rebooted - again no change.

This error seems to affect VB associated with the subform on the Purchase entry form I have created. I have set up code on the form itself which is not putting up the error message

by miss kitty

Why don't you list your code. It could be as simple as the connection string you are using could be in error or the database is expecting a userid and password to be passed to it.
Cathy

by al

On further investigation it appears that this error message appears when creating the Combo boxes - if the Name property is left as Combo x then the error appears - however if this property is renamed to say ProductID then the VB code runs - seems stupid to me - its just a variable name.

This discussion is closed to new replies.