ActiveX packaging
Hi All,
I would like to have 2 questions.
First of all, I made a package in which 3 applications are involved. All of them consist of a lot of ActiveX ( ocx, dll ) components. After installing the package on another machine either ActiveX components didn't work or I got a message: "Can't create ActiveX objects. I don't know what's wrong. Should I give permission for components in registry ?
Secondly, can I modify, set registry/folder permission by using native Visual Basic Script ?
Cheers,
J
I would like to have 2 questions.
First of all, I made a package in which 3 applications are involved. All of them consist of a lot of ActiveX ( ocx, dll ) components. After installing the package on another machine either ActiveX components didn't work or I got a message: "Can't create ActiveX objects. I don't know what's wrong. Should I give permission for components in registry ?
Secondly, can I modify, set registry/folder permission by using native Visual Basic Script ?
Cheers,
J
0 Comments
[ + ] Show comments
Answers (4)
Please log in to answer
Posted by:
kkaminsk
18 years ago
Posted by:
kkaminsk
18 years ago
I should say if you are missing dependant libraries you should launch the application with dependency walker and look for missing DLLs. If you have not used dependency walker it can be tough to get used to becuase some of the errors are not critical. Usually ignore any calls looking for localized DLLs if you are on an English OS and calls to kernel components that do not exist on on that OS. I.E you might see some DLL calls for Win9x kernel components.
Posted by:
kellerjanine
18 years ago
Posted by:
kkaminsk
18 years ago
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.