You probably have to delete the .exd files that are hanging around in the system. They'll be referencing the old code objects.

You can find them with this:

Dir *.exd /s

no difference with

1. delete EXDs

2.delete OE1100 OCX form and drop on new

Suspecting corruption in macro

found out client deleted an add-in to SEI and rebooted server

suspicious... I may reinstall PU8

VBA thinks OE1000 OCX does not support automation 

Thanks

no difference with

1. delete EXDs

2.delete OE1100 OCX form and drop on new

Suspecting corruption in macro

found out client deleted an add-in to SEI and rebooted server

suspicious... I may reinstall PU8

VBA thinks OE1000 OCX does not support automation 

Thanks

Some additional suggestions:

Ensure that you run the screen from the Sage desktop before attempting to run the macro with the screen embedded.
Run regacc.exe as administrator
Confirm that there is only 1 reference to the Runtime folder in the Path
Confirm that the Programs and Shared Data variables in the registry are correct

If you'd like a second set of eyes, feel free to send a zipped copy to [email protected]

that works

what the H E double hockey sticks!

I have in the past deleted EXDs, removed OCX and Reference and exit macro and then go back in and put back OCX and Reference

but this run without OCX step and then go back in  ----  that is out of the blue

thanks so much