Why would I set the AbtDatabaseParts “database” attribute to nil?
As the comment states, the intention of setting the ‘database’ attribute to nil is to “Clear the database connection to force re-validation of settings”. Prior to executing a query, the current algorithm used by database query parts to validate settings will only execute if the ‘database’ attribute is nil. For typical usages of the query parts, settings validation only occurs the first time the part is executed in order to validate the pre-saved settings. Subsequent query executions would occur without need to validate the part settings. The change that is causing you ‘grief’ was implemented to prevent walkbacks that occured when an application set the querySpecName to an invalid name, then attempted to execute the query. Setting the ‘database’ attribute to nil caused the setting validation routine to re-execute and report an error rather than causing a walkback. For your case, there seems to be an undesired side-effect. Potential solution… Setting the cached ‘database’ attribute to
