FIX: RDO BatchUpdate Causes Visual Basic 5.0 to Crash (190447)
The information in this article applies to:
- Microsoft Visual Basic Enterprise Edition for Windows 5.0
This article was previously published under Q190447 SYMPTOMS
Using an RDO Resultset BatchUpdate method against a Microsoft SQL Server
database when updating a Resultset with a large number of columns and long
column names, may cause Visual Basic 5.0 to crash with an Access Violation.
CAUSE
The BatchUpdate method generates a series of SQL statements in chunks to
send the updates to the backend database. The contents of each chunk is
affected by the following factors:
- The number of columns and rows involved.
- The length of the column names.
If the generated statement is too long, it will be truncated when stored in
the query buffer because of its limited buffer size.
RESOLUTION
There are three possible workarounds for this problem:
- Use shorter or longer column names.
- Use fewer rows per batch using the BatchSize property.
- Change the order of the columns when building the table.
Applying any of the workarounds changes the contents of each chunk based on
the ordinal position or order of the columns.
STATUS
Microsoft has confirmed this to be a bug in the Microsoft products listed
at the beginning of this article. This bug has been fixed in Visual Basic 6.0.
Modification Type: | Minor | Last Reviewed: | 3/2/2005 |
---|
Keywords: | kbbug KB190447 |
---|
|