custom action to set a property (type 51) in a merge module doesn't work

[NewsArchive]

Folks:
I'm finding that if I create a "type 51" custom action to set a
property - the results depend on whether or not the custom action is defined
in a merge module. If the custom action is defined in the merge module, the
property appears to not get set. But if I write the exact same custom action
in the main project, and call it from the same place I called the
merge-module custom action - it works fine and sets the property value.

BasicMSI installer, and IS 7.01.

Any ideas?

Thanx,
Lewis.

[NewsArchive]

This might be one of those cases where the actual MM property name as seen
from the parent install is property.guid.

"Lewis Gordon Pringle, Jr." <lewis@sophists.com> wrote in message
news:3c0d0e01@news.installshield.com...
> Folks:
> I'm finding that if I create a "type 51" custom action to set a
> property - the results depend on whether or not the custom action is
defined
> in a merge module. If the custom action is defined in the merge module,
the
> property appears to not get set. But if I write the exact same custom
action
> in the main project, and call it from the same place I called the
> merge-module custom action - it works fine and sets the property value.
>
> BasicMSI installer, and IS 7.01.
>
> Any ideas?
>
> Thanx,
> Lewis.
>
>
>