Hmmm. Maybe I should be blaming Onedaywhen for interrupting my blissful
ignorance.

DK

"Dave Peterson" wrote in message
...
But the problem is you never know unless someone warns you (just in time,
whew!)
or you see it in a different thread (too late, grrrrr!).

Dick Kusleika wrote:

OK, that's it. I'm done answering old posts. At least I got it right.

--
Dick Kusleika
MVP - Excel
www.dicks-clicks.com
Post all replies to the newsgroup.

"onedaywhen" wrote in message
om...
Dick,
Multiposts, don't you just love 'em:



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

--

"Dick Kusleika" wrote in
message
...
Ripan



Dim req As RequiredField

Set req = New RequiredField
Set req.Required = frmDataEntry.txtClaimantName


The problem is that the variable req falls out of scope when this
procedure
ends and the class is un-instantiated (is that even a word?)

Dim req at the top of whatever module sets it so that it persists
beyond
the
scope of that procedure. For instance, if you wanted to instantiate
the
class in your Userform_Initialize event, the module would look like
this:

Option Explicit

Dim req As RequiredField

Private Sub UserForm_Initialize()

Set req = New RequiredField
Set req.Required = frmDataEntry.txtClaimantName

End Sub

Having req as a module level variable will hold the class and it
will
work
as you expect.

--

Dave Peterson