Re: Vista Program Files Folder Problem - Issue 1

Vista does not permit saving data files to the Program Files folder. For
backward compatibility if an installation tries to place files there they
are redirected to a "virtualized folder" which actually resides in the
"C:\Users\User_name\AppData\Local\VirtualStore\Program Files\ MyApp" folder.
Storing data in the Programs Files directory has never been a good
practice and Vista actively prohibits it. The 'ProgramsData' folder in
Vista is intended for data storage.

The article below explains this and how to address problems like the one you
describe. See especially Scenario 3.

Common file and registry virtualization issues in Windows Vista
http://support.microsoft.com/kb/927387/en-us
--

"rac" <richard5@xxxxxxx> wrote in message
news:cfqdnU9gupspjo_UnZ2dnUVZ_sLinZ2d@xxxxxxxxxx
Jose,
I am encountering a similar issue.

I have been using a MS Access 2000 database for quite some time. I have a
user who purchased a new computer with Windows Vista (I needed to install
Vista Business to accommodate our network). The OS has been SP'd to SP1.

Very simply, I created a directory in Program Files and placed a front-end
MS Access database in it and a back-end database into a subfolder; both
are .mdb versus .mde. The user has been using this database for
evaluation and testing. In the meantime, I have been updating the
database application set on my WinXP/Access 2000 computer. To deploy the
updated database app, I simply copied the updated database set to replace
the existing set on the user's machine. When the database was opened on
the user's machine, the data displayed was that of the OLD database, not
the upgraded database. Sanity check... "user, watch me do this" Open db
app on my computer -- all as it should be. Copy files to network share
and copy them to user's machine from the share. Open the app on user's
machine -- OLD data.

I renamed the directory in the Program Files directory, manually created
the directory with the appropriate name along with the subdirectory, and
copied the database files into the respective directories. Now, with the
exact same update files as before, the database displays the NEW data.
Further, if I remove the new test directory and rename the original back
to the particular name, the database now opens with the NEW data.

I do see that no one has responded to your postings, at least into the
forum. I have experienced this before with complex, serious MS Access
issues. I hope you get a chance to see this follow up to your posting
over two months ago. If you have any thoughts or resolution, I would like
very much to hear from you.

rac
"José António Silva" <JosAntnioSilva@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:4A8C58D9-0AD4-4EBF-892C-D17249B89D33@xxxxxxxxxxxxxxxx
Hello,
I usually deploy a package composed, among others, by a mde file
(Compiled
Access File). The installation process is done with a msi file. So far so
good! However, sometimes, I need to update my program several times a day
and, to be simpler, I deploy to clients an exe file that just replace the
mde
file. This can break some windows installation rules, but that's enough!
Now, I'm doing this in four computers with Vista. Two of them are ok. In
the
other two, my exe file apparently replaces the mde, but when the final
user
run's it, he didn't get the last version that goes inside the exe file.
He
gets the same previous version.
I have given full control permissions to the folder c:\program files\my
program. I suspect from Windows Resource Protection, but I'm not sure and
I
don't know what to do or what to search for.

José António Siva




.

Relevant Pages

  • Re: Vista Program Files Folder Problem - Issue 1
    ... It had been very convenient to simply copy the files to their final locations using a batch script; I just now need to make my batch script a little bit smarter to place the data file into the virtualized folder. ... Storing data in the Programs Files directory has never been a good practice and Vista actively prohibits it. ... I created a directory in Program Files and placed a front-end MS Access database in it and a back-end database into a subfolder; ...
    (microsoft.public.windows.vista.security)
  • Re: question on 64 and 32 bit versions of Vista
    ... we have to Browse to the \Program Files ) folder and run the version of iexplore.exe that we find there. ... either the 32 bit or the 64 bit version of Vista you purchased. ... If you bought Vista Ultimate then both the 32bit and the 64bit installation ... If the Product key is an OEM key such as one that came with a sticker on the ...
    (microsoft.public.windows.vista.installation_setup)
  • Re: Autorisations in Vista
    ... many restrictions and nags as possible. ... "My Findings - VB6 Apps on Vista" ... It details experiments with installation. ... write to Program Files, so your own App.Path is locked ...
    (comp.lang.basic.visual.misc)
  • Re: Shell on Vista
    ... Many operations are not allowed on Vista. ... in Program Files before Vista and everything was working including writing ... I had to change installation ... admin rights, and another for the app itself because ...
    (microsoft.public.vb.general.discussion)
  • =?Utf-8?Q?Re:_Vista_Program_Files_Folder_P?= =?Utf-8?Q?roblem_=E2=80=93_Issue_1?=
    ... they have a free support service for Vista through March 2009. ... I have been using a MS Access 2000 database for quite some time. ... I created a directory in Program Files and placed a front-end ... I usually deploy a package composed, among others, by a mde file (Compiled ...
    (microsoft.public.windows.vista.security)
Loading