Hi Doug...hope you're having a good trip...please see my recent response to John K...strange (?), but looks like my problem is fixed...will have to look into it more today. Thanks for your input and help. J
>Jill,
>
>I'd call the cursor (view) first, then the table, and then do it again. I remember finding some obscure reference in one of the Q-articles and as soo as I get back into town I'll see if I can find it, ok? That will be in a couple days.
>
>BTW, I thought it was wierd as well....
>
>Best
>
>DD
>
>>Hi Doug,
>>
>>I'm STILL having trouble with this and keep going back to your message.
>>
>>>I ran into something similar a while back that might be related to what you're seeing. Essentially I ended up having to call the tableupdate function twice. In my case I had both the table and the view in the DBC and for some reason this was what was needed to make sure the update made it all the way to where it was needed.
>>
>>You mean "both the table and the view in the " DE of the form? and you're updating via the view? I'm using optimistic buffering for the view...what do you set for the table?
>>
>>And you call the TableUpdate for the View twice? or once for the table and once for the view - in what order?
>>
>>TIA, J