>i'm afraid to ask, but why would you need to create
> a copy of the object at runtime???

Now *that's* ominous. Makes me wonder if I'm being
daft, I don't think so.

We're using non-visual "business objects", classes
that represent our business data, seems sensible.

So, rather than stuff form controls with values
in the init method, we point the datasources of the
controls directly into the object, still sensible?

That means, for example, it would be very nice to
have a copy so that "abort" can put the object back
the way it was before the form was instantiated.

What d'you think? No, honestly please (but gently
of course :-) )

Mark