I'm not quite as "death on everything VB" as some of these guys, i.e. databound controls are really the guts of the greater VB concept of RAD and the reason VB was developed.

However there are a number of snags that relate to holdovers from earlier versions of VB before VB6, the grim spectre of DAO that still has it hooks too deeply into VB as of VB6, changes to Windows and to MDAC over the years, etc.


There are challenges involved in continuing to use VB6 today. The whole data binding arena is just one of them. You must be sure to use the latest VB6 service pack and then you have to adhere to the guidelines, detours, band-aids, etc. provided in MS KB articles over many years.

Even limiting ourselves to the ADODC we can find many KB articles. Here's an important one:

FIX: ADO DataControl and DataEnvironment Events Only Work with ADO 2.0

Another:

PRB: IRowsetNotify Error with ADO Data Control and ADO Recordset


The alternative is to sacrifice many of the RAD capabilities in VB6, and use it as if you were writing in a more primitive system like VBScript or C or something. This is fine for many hobbyists, since they aren't using it for what it was intended most of the time anyway: a RAD database front-end tool, similar to PowerBuilder and such. It even applies to many professional developers who don't want to spend all of the extra time and effort C/C++ require but want to create non-database programs in a higher level language.

There may be a resolution to your problem without the radical surgery of ripping out the ADODC and data binding. Without seeing some code it mgiht not be easy though, and even then the problem might relate to one of the subtle flaws introduced in the ecosystem since 1998.

Unlike MS Access, VB was never updated past VB6 to address these problems. All we have are the service packs and the suggestions in those KB articles to work with now.