IBDAC

Compatibility with Previous Versions

We always try to keep IBDAC compatible with previous versions, but sometimes we have to change the behaviour of IBDAC in order to enhance its functionality, or avoid bugs. This topic describes such changes, and how to revert the old IBDAC behaviour. We strongly recommend not to turn on the old behaviour of IBDAC. Use options described below only if changes applied to IBDAC crashed your existent application.

Values of the options described below should be assigned in the initialization section of one of the units in your project.

DBAccess.SQLGeneratorCompatibility:

If the manually assigned RefreshSQL property contains only "WHERE" clause, IBDAC uses the value of the BaseSQL property to complete the refresh SQL statement. In this situation all modifications applied to the SELECT query by functions AddWhere, DeleteWhere are not taken into account. This behavior was changed in IBDAC 2.00.0.4. To restore the old behavior, set the BaseSQLOldBehavior variable to True.

MemDS.SendDataSetChangeEventAfterOpen:

Starting with IBDAC 2.20.0.11, the DataSetChange event is sent after the dataset gets open. It was necessary to fix a problem with disappeared vertical scrollbar in some types of DB-aware grids. This problem appears only under Windows XP when visual styles are enabled.

To disable sending this event, change the value of this variable to False.

MemDS.DoNotRaiseExcetionOnUaFail:

Starting with IBDAC 2.20.0.12, if the OnUpdateRecord event handler sets the UpdateAction parameter to uaFail, an exception is raised. The default value of UpdateAction is uaFail. So, the exception will be raised when the value of this parameter is left unchanged.

To restore the old behaviour, set DoNotRaiseExcetionOnUaFail to True.

© 1997-2022 Devart. All Rights Reserved. Request Support DAC Forum Provide Feedback