=function() On Click Event refusing to work - on a subform...

[Knut Ole]

i get the following error:

"The expression On Mouse Move you entered as the event property setting produced the following error: A problem occurred while Access was communicating with the OLE server or ActiveX control."

the .OnMouseMove event for the control is set from a module, like thus:

 
             .OnMouseMove = "=rDraw(false," & cImg1.Name & "," & cImg3.Name & ")"
 

(this is working, ie. the control has this line of OnMouseEvent.)

the function i'm trying to call is declared thus and located in a module:

 
Public Function rDraw(fEdge As Boolean, varEdge As String, varBody As String)
Dim fX As Long
Dim coord As POINTAPI
Dim cmdLeft As Long
Dim cmdWidth As Long
 
(...)
 
End Function
 

for some reason, however, it's as if the OnMouseMove event can't find the function?! does anyone have experience with this kind of problem? is my syntax wrong? (i dont believe it is, as i've had it work once already manually. not able to replicate that anymore however.) or should i declare the function differently, or put it in a different module? (they should be accessible from anywhere, tho right?)

thanks a lot!

[dsatino]

Yes and no. If it's within a module you created then yes. if it's with a form module then:
Yes for any other code within that form module.
Yes for code outside the form module that references the form.
No for code outside the form module that doesn't reference the form.

[Stewart Ross]

When using string literals as arguments to the function you must enclose the literals in double quotes, otherwise the value passed will be misinterpreted at run-time as some kind of reference to an unknown entity. To use a double-quote within the string built in your code module you repeat the double-quote symbol three times, like this:

.OnMouseMove = "=rDraw(false,""" & cImg1.Name & """,""" & cImg3.Name & """)"

-Stewart

[Knut Ole]

thanks!
fixed the syntax, thanks! but it was actually a problem of a function i redeclared, upon which the old declaration (different name) "got stuck" in the formmodule, and it got messed up. brought out a fresh formmodule and everything worked fine. reproducable bug.
thanks again!