Hi Julie.

I am very intimate <g> with the MM framework. The v_ is just an alias that Kevin uses when opening the view so that local (lv_) and remote (rv_) views can be interchangeable in MM. This is not the source of the update problem that you are seeing. You can test your view outside your application by just opening the view and then making a change and issuing a TABLEUPDATE() from the command window.

HTH

Dan

>You may be on to something here. I am using MM framework, sort of. I used it to create objects to open views. The actual views are called LV_ but MM just uses V_ In my screen I am using V_ in to control source. Do you think tableupdate is confused by this naming?