I just read the full thread and see that the behavior was only not as expected due to the code not allowing the override of "no" so I guess there's no deeper issue and I'll try to make sure I read threads in the right order in future :)
On Jan 17, 2008 6:54 PM, Sean Corfield <[EMAIL PROTECTED]> wrote: > It just sounds like there's a deeper issue in terms of defaults...
