Hello
I'm using an OLE automation exe from another program. Starting the exe once as
a standalone application, it will register itself (or I could use the option
/regserver and it will not showup)
As what I thought, the only things that happens using the "/regserver" , is
that from the unique automation name and the GUID, it's updating within the
registry where this exe is located.
So, there are two places within the registry where it's updated:
1. Where the automation name is stored: result is a unique slsid as it's key
value
e.g. a name like "AcroAccess.AcroAccess" kas a key Clsid
{C523F39F-9C83-11D3-9094-00104BD0D535}
2. With this clsid it's reneration a key "LocalServer32" within the
\HKEY_CLASSES_ROOT\CLSID\ {..GUID..} \
(in the above example this will resolve in a 'localserver32 value "C:\Program
Files\Adobe\Acrobat 6.0\Reader\plug_ins\Accessibility.api"
We replace the existing exe by newer exe's. As what I would thought, there is
no reason rgistering the new exe again. It's physical places does not change;
therefor the above existing reference within the register would still be valid.
However, a lot of users without administrator access to the register-key's will
be prompted with a message "failing to register" (dutch text) after the exe has
been replaced by a newer version (GUID and automation name does NOT change
between versions).
My question: What exact happens when the /regserver process executes and is
there any explaination why a user (administrator) to have to re-register a new
version of the exe? I'm using Delphi 7.
Regards
Andries
[Non-text portions of this message have been removed]
