07-23-2008 03:37 PM
Hi I think I will become mad soon. I am programming application and I just add a 3D Graph. In the initialization process I set some parameters of it. When I open project, and run the top vi once everything works fine. When I run it again I get this error:
Error 3001 occurred at ActiveX Automation Not Implemented
I tried everything. I replaced the graph control with new one. That helped until I saved the top vi and run it again then the error appeared again.
I even tried to simplify my code with the aim to find where the problem could be. I was able to erase everything (code/controls…loop) except for the 3Dgraph and it's property node that causes this and I was still getting the annoying error. But when I saved this remaining code and run it again it worked as expected with no error. I repeated it many times and I was not able to figure out where is the problem.
Have anybody encountered this error? In addition the control behaves a little bit strange since sometimes the control appears out of the ActiveX container.
Thx a lot
07-23-2008 04:33 PM
I did a search for your error message and no match was found.
The code that you attached is not what you are referring to, is it?
R
07-23-2008 04:44 PM
07-23-2008 06:25 PM
07-24-2008 03:03 AM
07-24-2008 07:04 AM
This was the most difficult error I have ever encountered. It took me nearly three days to solve it. Finally I have to admit it was all my fault.
I have a vi that before the application runs it reads values of saved controls from ini file and updates those ctrls according to it(UI_INI_ReadFP). When quitting other vi saves these values into file(UI_INI_WriteFP) - to make it really simple I just get all FP controls names and values via method and I filter those that aren't important for me. I didn't filter out the 3D Graph control. So what it did was that during initialization it loaded the reference number, like 0x55600002, from the ini file(the file was written when the application was quitting during the previous run) and assigned it to the 3Dgraph control. It worked if I run the application for the first time. When I quit it and run it again it tried to assign the same reference number again which wasn't obviously possible but it didn't appear until I wanted to change the properties of the 3DGraph.
Grrrrr!
I wish I could rate myself with five stars 🙂
07-24-2008 07:20 AM
I got into a habit while raising my son that when ever I he would do something stupid and hurt himself I'd tell him "Don't do that!" I found myself doing the same thing last week while remodeling and I busted my head open on an old ventilation duct. So...
Don't do that!
Ben
PS your wish has been granted.
07-24-2008 07:47 AM
08-12-2008 09:53 AM
09-24-2009 03:03 PM
This was the most difficult error I have ever encountered. It took me nearly three days to solve it. Finally I have to admit it was all my fault.
I have a vi that before the application runs it reads values of saved controls from ini file and updates those ctrls according to it(UI_INI_ReadFP). When quitting other vi saves these values into file(UI_INI_WriteFP) - to make it really simple I just get all FP controls names and values via method and I filter those that aren't important for me. I didn't filter out the 3D Graph control. So what it did was that during initialization it loaded the reference number, like 0x55600002, from the ini file(the file was written when the application was quitting during the previous run) and assigned it to the 3Dgraph control. It worked if I run the application for the first time. When I quit it and run it again it tried to assign the same reference number again which wasn't obviously possible but it didn't appear until I wanted to change the properties of the 3DGraph.
Grrrrr!
I wish I could rate myself with five stars
Kudos from me! I just did essentially the same thing to myself. Thanks goodness I found this tread. Thanks for saving me three days.
I have a very generic util VI that will go through a list of VIs and save all the controls to a binary file, then it reloads them on the next launch. I didn't want to customize and start filtering controls, so I tried initializing the control (ActiveX container) back to default after it had been restored and this seems to be doing the trick. Phew.
Randy