BUG: RDO Rowcount May Be Wrong When Using rdAsyncEnable Flag (151815)
The information in this article applies to:
- Microsoft Visual Basic Enterprise Edition, 32-bit, for Windows 4.0
This article was previously published under Q151815 SYMPTOMS
When using rdoResultsets, the RowCount property is useful for determining
how many records have been returned by the query. Depending on the driver
and data source, the RowCount property returns either -1 to indicate that
the number of rows is not available, or 0 to indicate that no rows were
returned by the rdoResultset. If the driver is capable of returning a row
count, the RowCount property returns the number of rows in the
rdoResultset.
When opening an rdoResultset using the rdAsyncEnable flag, the RowCount
will always return 0. This could lead to the mistaken assumption that the
query returned no records.
WORKAROUND
If a Movelast is executed against the rdResultset before the RowCount is
queried, then the RowCount will be correctly set.
If the rdAsyncEnable flag is not passed to OpenResultset, the problem does
not occur.
STATUS
Microsoft has confirmed this to be an issue in the Microsoft products
listed at the beginning of this article. Microsoft is researching this
issue and will post new information here in the Microsoft Knowledge Base
as it becomes available.
REFERENCES
Visual Basic Online Help OpenResultset, RowCount
Modification Type: | Minor | Last Reviewed: | 7/14/2004 |
---|
Keywords: | kbbug kbDatabase KB151815 |
---|
|