FIX: Cannot Force Update Using a DataCombo Bound to ADODC or DE (193875)
The information in this article applies to:
- Microsoft Visual Basic Enterprise Edition for Windows 6.0
- ActiveX Data Objects (ADO) 2.5
This article was previously published under Q193875 SYMPTOMS
If a DataCombo box is bound to a ADODC or the Data Environment and you try
to force an update on the field that you changed in the DataCombo, it will
not Update the backend database.
RESOLUTION
There are some workarounds for this behavior that include adding this line
of code:
Adodc1.Recordset.Move(0)
instead of the Adodc1.Recordset.Update.
The Adodc1.Recordset.Move(0) will update the backend as soon as you issue
this command. Moving off of the record using the Adodc1.Recordset.MoveNext
or physically moving off the record by clicking on the navigation buttons
on the ADO Data Control (moving off of the record) will also force an
update.
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 with Visual Basic 6.0 SP3 and ADO 2.5.
Modification Type: | Major | Last Reviewed: | 10/16/2002 |
---|
Keywords: | kbADO250Fix kbbug kbCtrl kbDSupport kbMDACNoSweep kbVBp600fix KB193875 |
---|
|