>'In some more complex situations, the default update settings may not provide updates for a view you create through language...'
>
>They don't explain exactly what they mean by 'complex situations' but what I get out of this section is it's best to explicitly set your properties and don't leave anything to chance. That's what I do anyway.


I am working on my eView utility, which I would like to eventually be a functional and practical replacement for the view designer. So far it works pretty well, but this little tidbit is causing a few 'inconveniences'. I just wanted to avoid having to prompt the user to specify which table the field should be tied to. I guess this is what I will have to do.