An accessSetName event indicates a change in the name of a class in your application which is used to store the application specifications for your query, stored procedure and connection specifications.

A connectionAlias event signals a change in the connection spec, which contains the database manager and data source name for the query.

A dataManagerClass event indicates a change in name of the database manager.

A dataManagerName event indicates a change in name of the database manager.

A dataName event indicates a change in name of the database.

The destroyedPart event signals that the part and its children have been destroyed. Any system resources associated with the destroyed parts have been released.

An errorBlock event indicates a change in the block of code that's run when an error occurs in the data access code.

An executed event signals a change in execution status (whether or not the query has been executed).

A lastError event indicates the last error that occurred has changed.

The executedQuery event indicates that the query has executed.

The executedQuerySuccessfully event indicates that the query has executed successfully.

The executedQueryWithError event indicates that the query has executed successfully.

A packageSpecName event indicates the name of the database package specification that the query (and any necessary generated queries) will be stored in, has changed. A package specification is used to make SQL statements run as static SQL rather than dynamic. To ensure that all necessary SQL statements are generated and included in the package specification, you should set the value of packageSpecName only via the Multi-Row Query Settings window.

A querySpecName event indicates a change in the name of the query spec.

A self event indicates that the value of the target part itself has changed.