Program Files folder nightmare!

OK - I'm going nuts on deetermining the correct method of modifing files in
the "Program Files" folder. I have an Access application that installs the
MDE and other associated files into Program Files\AppName. These files are
packaged in an MSI file and used to install the app. However with UAC turned
on I can't update the MDE. The method I've been using is a self-extracting
zip file but I read where Vista requires that you use an installer to update
the Program Files folder. However, when I package the modification and
build a MSI file with a new MDE, it goes thru the process and appears to
have updated the folder with the new version but when you go to run it I
find it still has the old version.

What gives - I've scoured the web for solutions but nothing. If I rename
what appears to be the old version and run the re-named file I find that it
is the new version. This is very confusing.

Help!

Vic

"vic" <> wrote in message
newsF2A46EB-ACEC-4010-9A78-...
> OK - I'm going nuts on deetermining the correct method of modifing files
> in the "Program Files" folder. I have an Access application that installs
> the MDE and other associated files into Program Files\AppName. These
> files are packaged in an MSI file and used to install the app. However
> with UAC turned on I can't update the MDE. The method I've been using is
> a self-extracting zip file but I read where Vista requires that you use an
> installer to update the Program Files folder. However, when I package the
> modification and build a MSI file with a new MDE, it goes thru the process
> and appears to have updated the folder with the new version but when you
> go to run it I find it still has the old version.
>
> What gives - I've scoured the web for solutions but nothing. If I rename
> what appears to be the old version and run the re-named file I find that
> it is the new version. This is very confusing.
>
> Help!
>
> Vic


Vic,

Have you tried running the install msi as admin? (Right click on msi and
select Run As Administrator.)

Lang

"Lang Murphy" <> wrote in message
news:...
> "vic" <> wrote in message
> newsF2A46EB-ACEC-4010-9A78-...
>> OK - I'm going nuts on deetermining the correct method of modifing files
>> in the "Program Files" folder. I have an Access application that
>> installs the MDE and other associated files into Program Files\AppName.
>> These files are packaged in an MSI file and used to install the app.
>> However with UAC turned on I can't update the MDE. The method I've been
>> using is a self-extracting zip file but I read where Vista requires that
>> you use an installer to update the Program Files folder. However, when I
>> package the modification and build a MSI file with a new MDE, it goes
>> thru the process and appears to have updated the folder with the new
>> version but when you go to run it I find it still has the old version.
>>
>> What gives - I've scoured the web for solutions but nothing. If I
>> rename what appears to be the old version and run the re-named file I
>> find that it is the new version. This is very confusing.
>>
>> Help!
>>
>> Vic
>
>
> Vic,
>
> Have you tried running the install msi as admin? (Right click on msi and
> select Run As Administrator.)
>
> Lang

The option to "Run as Administrator" is not available on msi files. However,
I did convert the msi to an exe file and ran it as Administrator and id did
not help.

Vic

"vic" <> wrote in message
news:C80477F6-55EB-451E-955F-...
>
> "Lang Murphy" <> wrote in message
> news:...
>> "vic" <> wrote in message
>> newsF2A46EB-ACEC-4010-9A78-...
>>> OK - I'm going nuts on deetermining the correct method of modifing files
>>> in the "Program Files" folder. I have an Access application that
>>> installs the MDE and other associated files into Program Files\AppName.
>>> These files are packaged in an MSI file and used to install the app.
>>> However with UAC turned on I can't update the MDE. The method I've been
>>> using is a self-extracting zip file but I read where Vista requires that
>>> you use an installer to update the Program Files folder. However, when
>>> I package the modification and build a MSI file with a new MDE, it goes
>>> thru the process and appears to have updated the folder with the new
>>> version but when you go to run it I find it still has the old version.
>>>
>>> What gives - I've scoured the web for solutions but nothing. If I
>>> rename what appears to be the old version and run the re-named file I
>>> find that it is the new version. This is very confusing.
>>>
>>> Help!
>>>
>>> Vic
>>
>>
>> Vic,
>>
>> Have you tried running the install msi as admin? (Right click on msi and
>> select Run As Administrator.)
>>
>> Lang
>
> The option to "Run as Administrator" is not available on msi files.
> However, I did convert the msi to an exe file and ran it as Administrator
> and id did not help.
>
> Vic
>
>


Have you tried creating the app folder before running the msi and changing
permissions on it prior to running the install? I don't know if your app's
install will change permissions, but permissions on your app's folder would
be the next place I would investigate.

Lang

"Lang Murphy" <> wrote in message
news:404A8A48-EC9A-432C-8B10-...
> "vic" <> wrote in message
> news:C80477F6-55EB-451E-955F-...
>>
>> "Lang Murphy" <> wrote in message
>> news:...
>>> "vic" <> wrote in message
>>> newsF2A46EB-ACEC-4010-9A78-...
>>>> OK - I'm going nuts on deetermining the correct method of modifing
>>>> files in the "Program Files" folder. I have an Access application that
>>>> installs the MDE and other associated files into Program Files\AppName.
>>>> These files are packaged in an MSI file and used to install the app.
>>>> However with UAC turned on I can't update the MDE. The method I've
>>>> been using is a self-extracting zip file but I read where Vista
>>>> requires that you use an installer to update the Program Files folder.
>>>> However, when I package the modification and build a MSI file with a
>>>> new MDE, it goes thru the process and appears to have updated the
>>>> folder with the new version but when you go to run it I find it still
>>>> has the old version.
>>>>
>>>> What gives - I've scoured the web for solutions but nothing. If I
>>>> rename what appears to be the old version and run the re-named file I
>>>> find that it is the new version. This is very confusing.
>>>>
>>>> Help!
>>>>
>>>> Vic
>>>
>>>
>>> Vic,
>>>
>>> Have you tried running the install msi as admin? (Right click on msi and
>>> select Run As Administrator.)
>>>
>>> Lang
>>
>> The option to "Run as Administrator" is not available on msi files.
>> However, I did convert the msi to an exe file and ran it as Administrator
>> and id did not help.
>>
>> Vic
>>
>>
>
>
> Have you tried creating the app folder before running the msi and changing
> permissions on it prior to running the install? I don't know if your app's
> install will change permissions, but permissions on your app's folder
> would be the next place I would investigate.
>
> Lang

The initial install creates the app folder and everything is fine. The
problem is only when I need to send out a new MDE and I haven't been able to
replace the mde. I beleive the new version of the app is being sent to the
virtial store but I haven't been able to prove that. It seems the only
solution is to avoid using the Program Files folder.

<snip>
>> Have you tried creating the app folder before running the msi and
>> changing permissions on it prior to running the install? I don't know if
>> your app's install will change permissions, but permissions on your app's
>> folder would be the next place I would investigate.
>>
>> Lang
>
> The initial install creates the app folder and everything is fine. The
> problem is only when I need to send out a new MDE and I haven't been able
> to replace the mde. I beleive the new version of the app is being sent to
> the virtial store but I haven't been able to prove that. It seems the only
> solution is to avoid using the Program Files folder.

Hmm... could be... but... you didn't try changing the permissions -after-
the initial install?

Lang