Hi Tore,

Thanks for "jumping in". I believe that in general you're right, a good "naming convention" can help in many cases. Being a developer for many years I have no problem with that at all. However I'm afraid the classification of this specific issue is something different. In my case this is a TABLE change that requies CODE change in a an unexplained way: an index filter "FOR !deleted()" added to one table field (C1 in my example) triggers an irrelevant error on another field (C2).