Using Shockwave ActiveX Control

[bebbo]

I have created a small exe file to test a Shockwave object. This exe file works fine on my machine and on a seperate machine. However if I run it on the machine it is required for I get the following message:

Fatal Error Exception Code C0000005

I have installed Shockwave on this machine and installed Foxpro Runtime which includes Shockwave ActiveX Control. It is definately the Shockwave Control which is causing a problem as if I build the exe without the Shockwave Object the exe file runs.

Has anyone any idea to what the problem may be.

Thanks

 

[Scott24x7]

bebbo,
Has the ActiveX control been "Registered" to the machine? If you're using InstallShield, you need to include the control, and it will take care of the rest. If you're not, you'll need to *manually* register the control on the PC. (This is different from "Registration" of a program.) Once the control is properly registered to the system "Registry", it may solve your problem. Installins Shockwave does not necessiarly ensure that YOUR activeX control will be registered to the machine.

(Give that a try...)

Thanks,
-Scott

s-) Please let me know if this has helped s-)

 

[bebbo]

Thanks for that advise. I have created an setup file (from wizard) which includes the shockwave activex control. Should that automatically register it. If not how do I find out what file should be registered.

Once again thanks

 

[bebbo]

I have further news on my problem. It now appears the exe file works on Win98 but not NT. The program has been recompiled on Win NT but it still does not work on NT.

However should you run the program from source on NT machine it works. Run the same program using the exe file it does not work. The fatal error appears.

I really do not know where to go next. Any idea???

 

[chpicker]

Exception Code C0000005 is an Access Violation, which I've always taken to mean the program is trying to access an area of memory that it isn't supposed to and gets smacked by the OS. I've never known for sure, but that's what I've always thought.

I've never really been able to get around it. When it happens to me, it's usually because something got corrupted. I have to revert to a previous version of my source code and re-implement my changes.

I would suggest creating a new very simple project that includes ONLY what you need to run the ActiveX object and see if you still get the error.

Ian