Can't hit error point or breakpoint in RowSourceType UDF

P

Phlip

Newsgroupies:

I seem to think Access forms can submit to program control, like SDK dialogs
or VB forms. Harrumph.

I want to route the fields returned by the Select statement in my previous
post into a combo box.

This requires me to research a function with this signature:

Function find_ports(fld As Control, ID As Variant, row As Variant, _
col As Variant, code As Variant) As Variant

Y'all can Google for that.

So here I go using [augmented] Code-and-Fix; I copy that out of its post,
paste it in, point RowSourceType at it, and hit Go, expecting VBA can find
the integration errors faster than me.

Instead of getting the familiar "ding" and a breakpoint in that method, I
get an uninterceptible Access error message helpfully saying "'myUDF' may
not be a valid setting for the RowSourceType property, or there was a
compile error in the function."

The system seems to be valiantly defending my delicate constitution from the
sight of raw VBA. How do I get to the real error?
 
D

Dirk Goldgar

Phlip said:
Newsgroupies:

I seem to think Access forms can submit to program control, like SDK
dialogs or VB forms. Harrumph.

I want to route the fields returned by the Select statement in my
previous post into a combo box.

This requires me to research a function with this signature:

Function find_ports(fld As Control, ID As Variant, row As Variant, _
col As Variant, code As Variant) As Variant

Y'all can Google for that.

So here I go using [augmented] Code-and-Fix; I copy that out of its
post, paste it in, point RowSourceType at it, and hit Go, expecting
VBA can find the integration errors faster than me.

Instead of getting the familiar "ding" and a breakpoint in that
method, I get an uninterceptible Access error message helpfully
saying "'myUDF' may not be a valid setting for the RowSourceType
property, or there was a compile error in the function."

The system seems to be valiantly defending my delicate constitution
from the sight of raw VBA. How do I get to the real error?
Click to expand...

Did you try clicking Debug -> Compile in the VB Editor?
 
Top