We have a working Dcom package.. This is cause for celebration in our office!
But one little problem remains.. The Setup Wizard does not register the Remote Objects... Unless we manually double click the ActiveX exe on the Client workstation, we get an error "70 Permission denied".. When we run it & get to calling the remote..
Our Standard Exe Package does not include the .exe, but does contain the .vbr and the .tlb..(like we were told so that it will build a seprate ActiveX exe on the client c drive.. Now we are told the VBR contains the info in order to register the remote object.. It is obviously not doing it's job.. Is their something someone can think of that would cause this disconnect? or some way we can figure out what the VBR is doing & what it should be doing to debug the problem??
We fear someday deleting the program and not remembering to uninstall these personnally registered items.. We could delete the items and cause some real messyness..
Ann & Wenda
But one little problem remains.. The Setup Wizard does not register the Remote Objects... Unless we manually double click the ActiveX exe on the Client workstation, we get an error "70 Permission denied".. When we run it & get to calling the remote..
Our Standard Exe Package does not include the .exe, but does contain the .vbr and the .tlb..(like we were told so that it will build a seprate ActiveX exe on the client c drive.. Now we are told the VBR contains the info in order to register the remote object.. It is obviously not doing it's job.. Is their something someone can think of that would cause this disconnect? or some way we can figure out what the VBR is doing & what it should be doing to debug the problem??
We fear someday deleting the program and not remembering to uninstall these personnally registered items.. We could delete the items and cause some real messyness..
Ann & Wenda
