Are we talking about accessing objects on a "called" form? or a "calling" form. It's a little less bad to access child form properties, but I thought we were talking about accessing parent form properties.

Charlie gave you one great way to prevent the coupling. Mostly what you want to avoid is having your report object require the object calling it having a text box called txtDate and a spinner called spnCopies. If that is written into the report object, you won't be able to call it from some other process. Charlie's advice will help you prevent that.

M.


>
>I take your point here , but is there an altranative OOP way of doing thigs to access objects on a called form. This will happen all the time in ALL applications.
>
>Regards,
>
>Gerard
>
>>