(Boolean)
If true, the DataFind control will search the database using a numeric to alphabetic translation, using the numbers on a telephone keypad.
(Object)
This property identifies the data control to which the DataFind control is bound. This property, set using the Visual Basic Properties window, should be set before using any other property.
(Integer)
Specifies the type of database to be opened (ODBC, VB Data control, or set by code).
(String)
The Filter statement to be applied to an ODBC database. This statement can contain references to other control properties and thus allows a separate recordset to be created for each call.
See Filters (ODBC).
(Boolean)
If set, the control gets the complete count of records in the recordset when the control is entered by the main input. This may have a severe performance impact on large recordsets. Record counting terminates automatically if the count exceeds 500.
, MatchField,
MatchType
Used in conjunction with MatchData to search for a record meeting the criteria set by MatchData, MatchField, MatchAllChars, MatchType, and AlphaMatch. These are normally set by the Matching property page for this control.
(String)
The connect string used to open the ODBC database.
(String)
The table to be opened when using an ODBC database. The table name is used in a SQL statement generated by the control which opens the table and accesses the fields specified by the Fields object (the list of fields set by the Change Fields... button in the property page). This can be overridden using the Filter string when prefixed with a ">" character.
(Boolean)
Used in ODBC databases to indicate that the database should be opened in Read Only mode. This can provide an improvement in performance and should be used if no database updates are required.
(Integer)
Defines how to create the recordset when using ODBC databases. See Reviewing Recordsets for more information on recordset types.
There are three types of recordsets:
SNAPSHOT ( 0 )
DYNASET ( 1 )
FWDONLY ( 2 )
(Boolean)
If set, the DataFind control uses the same recordset position pointer for all channels. If using ODBC, one recordset will be created and shared by all channels.
When using a shared Recordset for all the channels, a lower performance might be experienced. For bigger Recordsets, performance could be boosted by easing the synchronization between channels (see GlobalDataSync INI setting). However, if an ODBC Recordset is shared in DataFind and its fields are being accessed from another control after a visible amount of time, the behavior is not expected and two or more channels may access the same record.