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.
Design-time use. Opens the form, converts all the normally data-bound controls to tag-bound (by removing the ControlSource property and writing a binding tag using that value), then saves the form.
Design-time use. Opens the form, converts all the tag-bound controls to normally data-bound (by removing the binding tag and writing the ControlSource property with the data bound column name), then saves the form..
Get the data binding group from a tag of form ::b0:CompanyName
Get data binding information from a tag of form '::b0:CompanyName' (read/write) or '::r0:CompanyName' (read-only)
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
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