Let me understand this:

By p-view you mean parameterized view?

Assuming this is the case, you are using (I assume) a parameter that returns zero-to-many records. Then you are adding records and trying to save. The view is not buffered.

Questions: what is the key field for the update? Is it the field which is the parameter?

Is this a local or remote view?

Also: why ISN'T the view buffered? If the view is not buffered then I believe the TABLEUPDATE() is redundant - when you move the pointer the view will update the base table automatically. Normally, in this type of situation I use Optimistic Table Buffering, make all the changes, and call TABLEUPDATE(2). Unless of course there is some reason that this wouldn't work for you.

Of course, I may not be understanding the problem here at all...

P.S. I've never found a good reason to use NOFILTER in an updatable view...

Eric Shaneson
Cutting Edge Consulting

>More on this saga:
>
>I added code to the routine that adds records to the view. When a record fails to tableupdate I SCATTER NAME to an array element and revert the record. When I'm done with my scan, I check to see if the array has any errors and then tries once more to create the record. Guess what? NOW IT'S NOT FAILING TO TABLE UPDATE ANYTHING! AAAAAAAAAAAAAAAaaaaaaaaaaaaaaaaaaaaaarrrrrrrrrrrrrrrrhh!
>
>>I have a private ds form with a form who's recordsource is a p-view. I've been having trouble adding groups of records. Specifically, one or more records might fail to tableupdate. I re-created my view to include the NOFILTER clause, and now no records fail the tableupdate on the view, but the source table isn't being updated.
>>
>>Do I create my view using the NOFILTER clause?
>>Do I open the p-view's source table in the de?
>>
>>TIA