Hi Andrea,

>I've had a similar problem sometime ago. I was using several instances of the same form to update different records, and I decided to go for the default data-session to reflect all changes by requerying only once. The trick was a custom property on the form to store the current record for each form instance...
>

The framework I am using has a feature that will refresh non-active forms when the user saves on the active form. You can elect to suppress this behavior as well. I think that this is pretty cool.

>
>Ohoh, I wonder if the view designer has been improved in VFP6....
>

I don't think so. Been following some other threads and Mr. Green doesn't seem to worried about that particular VFP feature.

Kendall