>I have not specifically told it to use table buffering. The view is part of the data environment in the form that should be displaying the updated data. I don't understand why the form that actually performs the INSERT does not have the view or the table in its data environment. Can you do a tableupdate after an Insert if the insert is to an actual table and not a view?
>

You can use TableUpdate on any cursor that is buffered, regardless of whether that cursor is based on a view or table. What is the setting of the DataSession property on the form that does the INSERT? If it is set to "Default Datasession", then it will use the same datasession as the form that called it. If not, then you must be opening the table and view in code somewhere. (Opening the view will open any source tables it uses.)

Also, check the Buffermode property of both forms, as well as the BufferModeOverride property of the cursors in the datasession. That will tell you if there's any buffering going on. Remember, views will always be buffered. The default for views is row buffering. You must specify table buffering if you want it.