DOCERR: More Info & Doc Fixes for FindFirst & Seek Methods (113903)
The information in this article applies to:
- Microsoft Visual Basic Professional Edition for Windows 3.0
This article was previously published under Q113903 SUMMARY
The status of database objects after a search operation (FindFirst or Seek)
is not clearly documented. Data Controls, Dynasets, and Snapshots all
maintain a valid record while Table objects actually have "No Current
Record" after an unsuccessful Seek (NoMatch = true).
In addition, there are two documentation errors: - The "Language Reference" manual gives incorrect information regarding
the FindFirst, FindLast, FindNext, and FindPrevious methods in the
second paragraph on Page 200:
If no matching records are found, the NoMatch property is TRUE and the
current record remains the same as before the Find method was used.
- The "Language Reference" manual gives incorrect information regarding
the Seek method in the first paragraph on Page 504:
NOTE: Always inspect the value of the NoMatch property of the
recordset to determine whether the SEEK method has succeeded. If it
fails, NoMatch is TRUE and the current record is unchanged"
Both statements are incorrect with regard to the position of the current
record. The behavior of the current record depends on the type of object
that has been used in the search method (FindFirst or Seek). The behavior
of Visual Basic data objects is outlined below.
Modification Type: | Minor | Last Reviewed: | 1/8/2003 |
---|
Keywords: | KB113903 |
---|
|