>I am in the midst of designing a form class which uses an Observer Pattern to communicate between forms. This would be useful if you have a form that has child records from a table on another currently open form. When you navigate through the records in the parent form you want the child records on the other form to be refreshed.
>
>I was curious if anyone has already set up a class similar to this?

I always use this kind of interface. Basically, any form carries primary/froeign keyvalue property and setcontrols method. Both of them set/called in Form.Activate event, i.e. if you want to refresh something in other form then the only thing to do is to shift focus there.