Difference between revisions of "Strange Errors & Behavior in VB6"
From Free Knowledge Base- The DUCK Project: information for everyone
m (→Automation error, The object invoked has disconnected from its clients.) |
m (→Automation error, The object invoked has disconnected from its clients.) |
||
Line 3: | Line 3: | ||
This error is not generated when the project is ran within the IDE. It is generated when the compiled exe is executed. | This error is not generated when the project is ran within the IDE. It is generated when the compiled exe is executed. | ||
− | Searching Google lead me down the wrong road thinking it was ADO related, as did the Microsoft Knowledge Base. It turns out the error was being generated by setting text in a ComboBox control. The error is, therefore related to the [ComboBox Control in VB6]. | + | Searching Google lead me down the wrong road thinking it was ADO related, as did the Microsoft Knowledge Base. It turns out the error was being generated by setting text in a ComboBox control. The error is, therefore related to the [[ComboBox Control in VB6]]. |
[[Image:AutomationErrorbyComboBox.png]] | [[Image:AutomationErrorbyComboBox.png]] |
Revision as of 21:40, 28 January 2008
Automation error, The object invoked has disconnected from its clients.
This error is not generated when the project is ran within the IDE. It is generated when the compiled exe is executed.
Searching Google lead me down the wrong road thinking it was ADO related, as did the Microsoft Knowledge Base. It turns out the error was being generated by setting text in a ComboBox control. The error is, therefore related to the ComboBox Control in VB6.
When ran in the Visual Basic IDE, the error is NOT generated. The error is only generated in the compiled exe version of the project. Debugging within the IDE alone is not helpful. The error was tracked down using a series of MsgBox messages.
Setting the default value to the cboBox like this is probably not "by the book".
Key terms:
- circular references