Hi,

we have an application that runs in a "safe" mode where the user can
only use our application (and only particular features depending on
his user rights) but cannot start other applications.
Our "File open" dialogs are old style and do not allow to change file
names or to delete files.

Now we would like to display a PDF file. Simply using e.g. Acrobat
Reader is not possible because e.g. it has new style file open dialogs
and will start a browser when using the help/online help capabilities.

One idea is to create our own application that uses the Acrobat
ActiveX control to provide a PDF viewer with limited capabilities.
However, it seems that even so the critical capabilities are still
available to the user.

Is there a straightforward and "offical" way to constrain an ActiveX
control so that it e.g. cannot create another process /start another
application etc.?

(our app would be implemented in Visual Studio 2005 using either C++
or C#)

Any advice welcome.

The company I am working for are currently updating Adobe Reader
installations from Acrobat 5.x to Reader 8.x.
However, we will run in to an issue with an older application, for
which we no longer have the source code.

The issue is that Acrobat 5 and 6 both came with PDF.OCX, which was
used quite a bit in our applications. Reader 8.x has replaced this
with AcroPDF.DLL, which means that compatibility has been lost.

I can wrapper the relevant control in AcroPDF.DLL in to a new PDF.OCX
with the same ProgID, functionality and accessors, but this does not
help as I need to also set the UUID, to keep the older applications
unaware of any changes.

Does anyone know a way of setting the UUID for a VB OCX, or are you
aware of a work around for an issues like this?

Many thanks,

Kev K

ohvxsozqfhmqfvphltgej

War, famine, global warming, climate change, disease and so much more.

How will YOU cope?

Every once in while I let people know of this forum, where real people, like you and me,
get together and discuss how to deal with these things as best as we can.

http://groups.yahoo.com/group/misc_survivalism_moderated/

Check it out.

Dana

We implement an Activex component and sign the component, etc.

I want it work like an Applet with respect security.
e.g. If a html page has an applet, it is instantiated in that page and
the javascript can use that applet the applet life cycle ended when
we move to new page.

As I understand it, ActiveX component is downloaded and registered to
windows registry with respect to our implementation of
DllRegisterServer in the component. We implement
DllUnregisterServer() also.

But When you move to new page IE does not call unregister this
component?

What am I doing wrong? if not how to achieve like this?

Can a component call unregister it self explicitly?

Regards
Krishna