David,
I think it is. It only shows "if table is exclusive then no bloat occurs" is wrong.
Cetin

>Cetin,
>
>That really isn't a valid test for cursor memo bloat. There's a 50/50 chance that each replace is going to require a new memo block allocation because the memo field is longer, so of course you'll see a big file constantly growing but it doesn't have 1000 memo block allocations in it.
>