P
(PeteCresswell)
I tried posting this in microsoft.public.activex.controls,
but no luck.
Upon reflection, it seems better suited to .access because
it seems to be something about how MS Access VBA handles
a certain type of error.
---------------------------------------------------------
This error starts popping every so often following changes to
various VBA routines (not to NodeClick, however) in the same
form.
Something about "The expression NodeClick...."
Screen snap at: http://tinyurl.com/2pmbne
I'll revert to the prior version, key in the same changes, and
all will be well.
It does not trigger my error trapping, which looks for Err<>0.
The VBA code always compiles, and I compact/repair several times
per day while developing.
Only theory I can come up with is that something on the form is
borderline corrupt.
But why does the VBA code compile and Err=0?
Can anybody shed some light?
but no luck.
Upon reflection, it seems better suited to .access because
it seems to be something about how MS Access VBA handles
a certain type of error.
---------------------------------------------------------
This error starts popping every so often following changes to
various VBA routines (not to NodeClick, however) in the same
form.
Something about "The expression NodeClick...."
Screen snap at: http://tinyurl.com/2pmbne
I'll revert to the prior version, key in the same changes, and
all will be well.
It does not trigger my error trapping, which looks for Err<>0.
The VBA code always compiles, and I compact/repair several times
per day while developing.
Only theory I can come up with is that something on the form is
borderline corrupt.
But why does the VBA code compile and Err=0?
Can anybody shed some light?