>Gregory,
>
>If this were 40 years ago I would right away jump to every suggestion (or idea) brought about and start coding. But now that I am older and wiser (some may disagree though) I am thinking of all possibilities and mainly about creating a maintenance nightmare (which I am very good at). There is one more option that we didn't discuss; I could say to customer, Sorry, I can't do it. I am learning to say No; it is a work in progress and painful but in the end very rewarding <g>.
>
>I will consider, of course, everything you suggest. Thank you very much!
>

Dmitry,

BindEvent is well worth the time investigating.

I've set up a whole 'system' that does a lot of checks as the user changes amounts on a balance sheet

Each line in a grid has an image. If it becomes red, the user can move the mouse over it and see what is wrong

[ image attached for a glance ]

The only thing I do is add that class to the form in the init.

From there on the form raises events (= call form's methods to which the class subscribes) and the class raises events

If I do not add that object to the form, then there are no checks done. The form continues to raise events, but there's no one to listen to them

So - take some time to try out BindEvent