Hi Jamie,

I figured the user defined type is what set the cat amongst the pigeons, and
for some reason only the specific combination of passing by reference to a
local method, then to a UserForm class property setter (or in VB do you guys
call value type setters, letters? ;-)

When running my full application as an Excel Add-In I was getting the
following automation error:
Automation Error: The Object Invoked Has Disconnected from Its Clients

That makes me think there is something sinister going on in the background
somewhere, since the code itself should be pretty harmless.

Anyway, I've taken the route of a module level variable of the user defined
type, then passing that once only to the form class via its associated
property. Seems to work fine.

Cheers,
Wayne.



"Jamie Collins" wrote in message
om...
keepITcool wrote ...

ok i confirm it crashed in xlXP too :)

but what's the point?

the PROBLEM is that
you're treating a userform as a class module (first time i saw that :)

That isn't the problem! Userforms *should* be treated as classes. You
should read my posts more often ;-)


http://groups.google.com/groups?selm...g .google.com

AFAIK it's the user defined type that is the problem. I've seen it
before in this ng but don't have any answers other than workarounds
(which the OP already has).

Jamie.

--