Form Data Binding

These allow form databinding to be done using tag strings rather than the ControlSource property. The advantage is that the user has complete control over when and how the data is read and written. Also, multiple datasets can be bound to a single form by using different binding groups.
These functions used to support automatic validation by using schema information, but they have now been greatly simplified. Shadow Tables methods are the encouraged editing method since they work for continuous forms and provide many other benfits.

Public Function ReadBoundControlsFromDb(f As Form, sqlStr As String, Optional BindingGroupNum As Integer = 0 , Optional UseExtendedRSType As Boolean = False, Optional SuppressError As Boolean = False) As Boolean

Read data from single-record SQL result set to controls identified by tags of form "Bx:FieldName" where x is the group number Optionally "Rx:FieldName" reads the data but does not write it later (good for comparison copies of data for 'dirty' checks) Error occurs in ODBCDirect workspace connection dbOpenForwardOnly recordset where a memo column is returned In this case, call with UseExtendedRSType=true

Public Function WriteBoundControlsToDb(f As Form, sqlStr As String, Optional BindingGroupNum As Integer = 0, Optional UseExtendedRSType As Boolean = False) As Boolean

Read data from single-record SQL result set to controls identified by tags of form "Bx:FieldName" where x is the group number Optionally "Rx:FieldName" reads the data but does not write it later (good for comparison copies of data for 'dirty' checks) Error occurs in ODBCDirect workspace connection dbOpenForwardOnly recordset where a memo column is returned In this case, call with UseExtendedRSType=true