On Click event property error when opening a form

[Dave_D]

I started getting the following error when I clicked on an event named "NEW ISSUE" and can not find a solution thru Goggle.



The expression On Click you entered as the event property setting produced the following error: A problem occurred while Microsoft Access was communicating with 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

I also receive On Current..... when I try opening my form named "ISSUE LIST" where the event of "NEW ISSUE" resides.

I tried upload the DB (896kb) by it's limited by size restrictions

Any advise either uploading the DB or on the error message.

Thanks!

[Bob Fitz]

Before uploading Compact and repair and then Zip the db

[davegri]

When I get that message it indicates corruption.
Create a blank database and import EVERYTHING from the broken db into the new one, using the ribbon: External Data>New Data Sources>From Database>Access
Compact/Repair the new database and it should be OK.

[Micron]

I have experienced this. It was due to a posted db being created in a locale that was totally foreign to mine. If I switched to that locale, it was fine. Not something I like doing though.
That you say can not find a solution thru Goggle. could mean that you tried things that didn't work. It might be helpful to know more about that. Also might help to know about what changes were made before this started, or maybe where the db hails from, or if the event is on a subform which references a main form control upon Open or Load. Main form controls are not available to subform Load or Open events.

[ssanfu]

I got these errors when the VBA project corrupted. I finally discovered how to recover but it was a tense 5 days....

[Dave_D]

First off, I now attached the DB to this posting. Secondly, I took those who suggested making a fresh copy of the DB, but after doing so, I received the same error message. The one thing that I did notice with the fresh copy was, when I removed the form "NEW ISSUE", I no longer received that error message. It has to do something about the properties of the form "NEW ISSUE".

[Bob Fitz]

First off, I now attached the DB to this posting. Secondly, I took those who suggested making a fresh copy of the DB, but after doing so, I received the same error message. The one thing that I did notice with the fresh copy was, when I removed the form "NEW ISSUE", I no longer received that error message. It has to do something about the properties of the form "NEW ISSUE".

No file attached

[moke123]

although I haven't spotted the error yet, You need to add option explicit to all your modules.

[davegri]

Attachment 34625

Imported into new DB as I suggested in Post #3, and it seems fine.

[Dave_D]

Bob, I have to disagree; I see the attachment and was also able to open it.

[Dave_D]

davegri, I'll try it again. Thanks!

[Dave_D]

davegri, This time it worked just fine and without any error message. Thank you so very much and to all that helped, Thank you as well!

[moke123]

Its important that you add option explicit to all your modules. When i added it to your original db it threw an error.
Please take a look at this link...http://www.fmsinc.com/microsoftacces...ons/index.html

[Micron]

Alas, what *all of such web pages don't but should explain is that improper use of the bang operator won't be caught by Option Explicit and compiling code. Suppose the form control name is txtOrderId. Me.txtOrdreId will be caught. Me!txtOrderId will not. The latter causes late binding, which means it is only interpreted at run time.

*At least none that I have read.