Vista - Vista 64bit rpeventing file copy

10-15-2009

This looks really promising. I will test this one out.

Thanks
Tony

"FromTheRafters" <erratic @nomail.afraid.org> wrote in message
news:uFGd$gySKHA.4360@newsgroup

Quote:

> Check to see if your "new code" is being saved into a virtualized "Program
> Files" within the user's profile.
>
> See this also,
>
> http://support.microsoft.com/kb/927387
>
> "Tony Vrolyk" <me@newsgroup> wrote in message
> news:%23kmLrMtSKHA.4592@newsgroup

Quote:

>> This seems the most promising direction. I did some quick looking up and
>> MDE files are one that is protected. I don't understand why Windows would
>> consider my app a protected file but it seems to fit the pattern. The
>> solution according to what I found it to create my updates as bona fide
>> installers and not just a simple file-copy.
>>
>> I will test this out. Thanks for the help.
>>
>> Tony
>>
>>
>>
>> "FromTheRafters" <erratic @nomail.afraid.org> wrote in message
>> news:e2mthceSKHA.4324@newsgroup

Quote:

>>> Read up on Windows Resource Protection (WRP) to determine if your file
>>> is being "protected". Userland users may experience silent protection
>>> whereas as an administrator they might get an error message (<--clue).
>>>
>>> "Tony Vrolyk" <me@newsgroup> wrote in message
>>> news:eC1jkobSKHA.3540@newsgroup
>>>>I sell a program that I wrote in Access and have had a couple customers
>>>>with 64 bit versions of Windows Vista where if I send them an updated
>>>>file, via email or download, it appears as though the file has copied
>>>>over the old version but when they run the program it is still the old
>>>>version of the program. Is there some underlying copy protection that is
>>>>preventing me from copying over the file yet does not report any error
>>>>or security warning?
>>>>
>>>> Here are a couple details
>>>> * The original install program installs the Access runtime, my program
>>>> and related system files. The program itself is made up of two files.
>>>> one Access MDE (like a read-only Access file that contains all the
>>>> coding) and a database file.
>>>> * I then sent them an update which consists of a zip file that contains
>>>> a new MDE. They are to copy that over their existing MDE in order to
>>>> use the new version.
>>>> * In one instance I was able to remote into the customer's PC and do
>>>> the file copy it myself. I can see the file copy, the file size and
>>>> date appear to be correct for the new version but when I would run it
>>>> it would run the old code. Ths PC was an HP laptop if that makes any
>>>> difference
>>>>
>>>> This is driving me batty. Does anyone have any ideas?
>>>>
>>>> Thanks
>>>> Tony
>>>>
>>>>
>>>>
>>>
>>>

>>
>>

>
>

10-15-2009	#11 (permalink)
Tony Vrolyk n/a posts	Re: Vista 64bit rpeventing file copy This looks really promising. I will test this one out. Thanks Tony "FromTheRafters" <erratic @nomail.afraid.org> wrote in message news:uFGd$gySKHA.4360@newsgroup Quote: > Check to see if your "new code" is being saved into a virtualized "Program > Files" within the user's profile. > > See this also, > > http://support.microsoft.com/kb/927387 > > "Tony Vrolyk" <me@newsgroup> wrote in message > news:%23kmLrMtSKHA.4592@newsgroup Quote: >> This seems the most promising direction. I did some quick looking up and >> MDE files are one that is protected. I don't understand why Windows would >> consider my app a protected file but it seems to fit the pattern. The >> solution according to what I found it to create my updates as bona fide >> installers and not just a simple file-copy. >> >> I will test this out. Thanks for the help. >> >> Tony >> >> >> >> "FromTheRafters" <erratic @nomail.afraid.org> wrote in message >> news:e2mthceSKHA.4324@newsgroup Quote: >>> Read up on Windows Resource Protection (WRP) to determine if your file >>> is being "protected". Userland users may experience silent protection >>> whereas as an administrator they might get an error message (<--clue). >>> >>> "Tony Vrolyk" <me@newsgroup> wrote in message >>> news:eC1jkobSKHA.3540@newsgroup >>>>I sell a program that I wrote in Access and have had a couple customers >>>>with 64 bit versions of Windows Vista where if I send them an updated >>>>file, via email or download, it appears as though the file has copied >>>>over the old version but when they run the program it is still the old >>>>version of the program. Is there some underlying copy protection that is >>>>preventing me from copying over the file yet does not report any error >>>>or security warning? >>>> >>>> Here are a couple details >>>> * The original install program installs the Access runtime, my program >>>> and related system files. The program itself is made up of two files. >>>> one Access MDE (like a read-only Access file that contains all the >>>> coding) and a database file. >>>> * I then sent them an update which consists of a zip file that contains >>>> a new MDE. They are to copy that over their existing MDE in order to >>>> use the new version. >>>> * In one instance I was able to remote into the customer's PC and do >>>> the file copy it myself. I can see the file copy, the file size and >>>> date appear to be correct for the new version but when I would run it >>>> it would run the old code. Ths PC was an HP laptop if that makes any >>>> difference >>>> >>>> This is driving me batty. Does anyone have any ideas? >>>> >>>> Thanks >>>> Tony >>>> >>>> >>>> >>> >>> >> >> > >
My System Specs

Similar Threads
Thread	Forum
can't delete / move .exe file after it is run in vista 64bit	General Discussion
vista can't copy large files? another XP file-copy bug?	Vista General
File Sharing with Vista 64bit is REALLY SLOW!	Vista networking & sharing
vista stops install after file copy before 'file gathering' no err	Vista installation & setup