The DblClick event worked ok in 3.x. But in 4.7 it seems to cause problems.

I noticed that the parameter list changed from 3.x to 4.7. Even accounting for that, if the event is present in code -- even if it is the only piece of code -- Access 2010 complains that it conflicts with other events, even if those events are not coded. Here's a typical message: "The expression MouseMove you entered as the event property setting produced the following error: Procedure declaration does not match description of event or procedure having the same name." I'm not trapping for a MouseMove event.

Then additional conflicts are reported complaining of the same issue with other events that I am not using. I am not trapping any of the events complained about.

Here is the event code:

Private Sub iGrid0_DblClick(ByRef Button As Integer, ByRef Shift As Integer, ByVal x As Single, ByVal y As Single, ByVal lRow As Long, ByVal lCol As Long, ByRef eAction As EDblClickAction)

' code here

End Sub

I even tried changing the data type of eAction to Long and Integer, but it produced no different result.

I look forward to a prompt resolution. This is a killer for me.

Thanks.

To tell you the truth, you are the first who reported this problem.

As we can judge from your description, you switched from iGrid 3.0 to 4.7 in your MS Access db, and there can be a mix of things related to both iGrid's which prevents your mdb from working properly.

The first thing that came into my mind is to check the project references - the Tools\References menu item in the VBA window (ALT+F11). Did you know that when you add an ActiveX control to your form in an MS Access database, a reference to the corresponding type lib is added automatically? Most likely, you have a reference to the iGrid v3.0 OCX there, and you need to remove it (uncheck).

If that does not help, send us please a problem mdb file for the further consideration.

Igor cleared this up offline.

I was using the event parameter list from the online help file, which apparently is wrong.

Inserting the event subroutine using the drop down list of events from within VBA provides the correct syntax.

I want to thank Igor for his prompt, gracious, and clear explanation. Great support!

I was using the event parameter list from the online help file, which apparently is wrong.

We checked the CHM help file - yes, our fault, the signature of the DblClick event should be corrected (the two first parameters are passed ByVal but not ByRef as the help file states).

We'll check the definitions of other events and correct this issue and other events (if any) in the CHM file in the nearest future. We're going to publish the fixed help file as soon as this work is done.