Graham,
do you have a link/reference for "... Windows virtualizes ... also (astonishingly!) C:\ProgramData" as if it is so, and I've understood you correctly, I'm going to be a little embarassed and perplexed.
One Installation constellation of my Access Application is to ProgramData and I personally have a lot of stuff in my ProgramData Directory but the only thing reflected into the Virtual Directory is something from NVidia, from 2009.
"C:\Users\All Users" is a symbolic link to "C:\ProgramData" so virualising things out of there into somewhere else seems strange but stranger things have been known.
TIA, Andrew
--- In MS_Access_Professionals@yahoogroups.com, "Graham Mandeno" <graham@...> wrote:
>
> Hi Mike
>
>
>
> You should never install an Access application in Program Files on any
> system with Vista or later. The reason is because of a "security feature"
> known as "virtualization" which is intended to protect users from themselves
> but actually causes more problems than it solves.
>
>
>
> What happens is this: If a process which is NOT running "as Administrator"
> tries to write to a file under C:\Program Files, the system makes a copy of
> that file in a "virtual" folder. This folder is located in a corresponding
> subfolder under C:\Users\<username>\AppData\Local\VirtualStore\Program
> Files. Any subsequent reference to that file uses the "virtual" copy, not
> the "real" one.
>
>
>
> Of course, Access always updates a database file and changes its modified
> date every time it is opened, so the FIRST time you open your front-end
> after installation it gets virtualized, and subsequent uses open the copy.
> Now, if you update the front-end with a new copy (installed "as
> Administrator" by your setup program) then the "real" copy will be replaced,
> but the "virtual" copy (the old version) will continue to be used.
>
>
>
> As well as C:\Program Files, Windows virtualizes the C:\Windows folder and
> also (astonishingly!) C:\ProgramData. I say astonishingly, because
> C:\ProgramData is intended for storing data which is shared by all users.
> However, the moment a user writes to a file, the system creates a private
> copy and the changes never get seen by other users!
>
>
>
> So, in short, avoid putting any updateable files in any of these three
> virtualized folder trees.
>
>
>
> I don't see how this could be causing your problem, but it may be that the
> user is actually opening an old copy and not the one you have installed.
> Also, I don't believe that C:\Program Files is *automatically* a trusted
> location as far as Office is concerned.
>
>
>
> Best wishes :-)
>
> Graham
>
>
>
> From: MS_Access_Professionals@yahoogroups.com
> [mailto:MS_Access_Professionals@yahoogroups.com] On Behalf Of mike
> Sent: Tuesday, 31 July 2012 09:05
> To: MS_Access_Professionals@yahoogroups.com
> Subject: [MS_AccessPros] Re: Access 2007 ribbon not showing in Access 2010
>
>
>
>
>
> Yes, the data files are distributed using a setup .exe file that installs
> them in the Program Files directory of the computer. Great question though,
> thank you.
>
> Mike
>
> --- In MS_Access_Professionals@yahoogroups.com
> <mailto:MS_Access_Professionals%40yahoogroups.com> , "Bill Mosca"
> <wrmosca@> wrote:
> >
> > Mike
> >
> > Do your clients have the database file(s) in a trusted location?
> >
> > Regards,
> > Bill Mosca, Founder - MS_Access_Professionals
> > http://www.thatlldoit.com
> > Microsoft Office Access MVP
> >
> https://mvp.support.microsoft.com/profile=C4D9F5E7-BB03-4291-B816-6427073088
> 1E
> > My nothing-to-do-with-Access blog
> > http://wrmosca.wordpress.com
> >
> >
> >
> > --- In MS_Access_Professionals@yahoogroups.com
> <mailto:MS_Access_Professionals%40yahoogroups.com> , "mike" <akcam2006@>
> wrote:
> > >
> > > I have a custom ribbon I built using XML in Access 2007. It seems to
> work just fine on my computer with Access 2010 but when most of my clients
> open the file on their computer's using Access 2010 the ribbon will not
> display. The only help I could find on the internet about this issue warned
> me about the case sensitive nature of the ribbon in Access 2010, something
> that apparently didn't affect Access 2007. I have checked all my XML and VBA
> and everything seems to match up. Any other thoughts as to what could be
> causing the issue?
> > >
> >
>
>
>
>
>
> [Non-text portions of this message have been removed]
>
Tidak ada komentar:
Posting Komentar