No usually, it's only when I've done something really bonehead. So, mostly the checks are there for me while developing (and in case something goes wrong for the user, of course).
I've never had tableupdate() return .f. in a normal data update/add mode.

I've tried 0,1, and 2 (never have figured that sucker out.)
>>3. I knew there was a problem because TABLEUPDATE( 0, .T., 'lvw_wlevel') returned .F. on just a few records. And only when I was creating more than 30 or so.
>I always use 1 as the first parameter.

Oh, I'm not resting easy! Just need to get something to my tester so she could make some progress while I keep tormenting myself. I'd really like to know _exactly_ what's happening. Especially since I'll be leaving in a couple of weeks _and_ because it's my first real go at p-views for grids. :-( I don't *think* it's the RI. That's my first suspicion, but I've been through it several times and I haven't found anything squirrelly yet. Maybe I'll refocus there, though...Oh, I haven't found anything different yet, and it's not always the same ones. :-((((
>*shiver* that's the kind of code that always comes back to bite me, I usually try to figure out the real root problem. Do you have table/field/RI rules that are causing tableupdate() to choke on some records? What's different about the rejected records vs accepted records?

Thanks for the suggestions, David.