Hi 

Our standard practice is to use views in datawindows for retrieval.  This avoids putting complex SQL in datawindows. It also allows to change the view behind the scenes if we decide to use different tables in the view. 

We have to specify the update properties in the DW painter because of using a view, but benefits of views vastly outweigh having more complex SQL in the datawindow. 

If the select statement is changed to add in another column, the update properties then get trashed and have to be re-entered. I'm not sure why this is the default, as adding in an extra column shouldn't impact this. If SP update is being used, it's even more hassle.

If the default was to leave the update properties as is, this would be far better as it would probably be OK in around 99% of cases, compared to trashing them, where they need to be re-instated in 100% of cases. 

PB has operated like this for years, so we're used to it, but I've found Appeon very responsive, so thought it might be worth raising it.

Cheers

Jim