Using vbNullString with controls and command bars

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   I have found an issue when using the command bars and combo boxes in the latest version of the code jock controls. 

If you add an item to a combo box with a value of vbnullstring you get the following error message 

Automation Error, The object invoked has disconnected from its clients error

If you use "" instead of vbNullString then the error doesn't present its self. 

This also happens when you Add an item to a command bar with vbNullString as its name. and the same fix works where you can replace vbNullString with "". 

I have attached a code example illustrating this issue. The code needs to be compiled in order for the error to be displayed and it also has to be ran on a computer that hasn't had codejock installed. Running the example from the vb6 IDE will not display this behaviour and running it on a development machine with CodeJock installed on will not display this behaviour either. 

uploads/7709/vb6projectProject1.zip

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
DMoreland Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 05 November 2012 Status: Offline Points: 2	Post Options Post Reply Quote DMoreland Report Post Thanks(0) Quote Reply Topic: Using vbNullString with controls and command bars Posted: 13 November 2012 at 7:00am
	I have found an issue when using the command bars and combo boxes in the latest version of the code jock controls. If you add an item to a combo box with a value of vbnullstring you get the following error message Automation Error, The object invoked has disconnected from its clients error If you use "" instead of vbNullString then the error doesn't present its self. This also happens when you Add an item to a command bar with vbNullString as its name. and the same fix works where you can replace vbNullString with "". I have attached a code example illustrating this issue. The code needs to be compiled in order for the error to be displayed and it also has to be ran on a computer that hasn't had codejock installed. Running the example from the vb6 IDE will not display this behaviour and running it on a development machine with CodeJock installed on will not display this behaviour either. uploads/7709/vb6projectProject1.zip