>I don't want to close my view because the same view is used on multiple forms, the people I work for put 2 forms of fields in one table and scattered some other fields from 1 table throughout multiple forms. I didn't think anything of it because I just added the same view to multiple forms. So I have the Borrower view on 3 forms and if it gets closed on one then it messes up the other forms in which it is a part of their data environment. Is there a problem with that?!

I don't see why there should be, but I DO think you have some design problems - caused by 'pre-existing data structures'.

First, look at your overall plan to see where this view is opened - By a single form when the user picks the client he's working on? If so, then all references to opening/closing can be eliminated from other forms.

Second, can you open the view, Browse it, make a change, save it and close the view without errors (no forms open at all).

Third, are you using subclassed forms - either your own subclasses or a framework? If so, there may be code you are unaware of which is opening/closing or updating views.

Fourth, can you open this view, then open a single form and close it without errors?

Fifth, can you do the same thing with a couple of field updates?

These tests might give you an idea whether it's the view or the forms.

Time for me to log off for the night - even though I'm an hour 'younger' than you. More tomorrow if you wish.

Barbara