Prev: VB6 With/End With - how to pass the object itself?
Next: Debugging Tricks : Going Blank
From: mayayana on 3 Mar 2010 13:20
> Take these two examples to explain my question
> Using MS Word 2002 on Windows 7
> I open word, type some text and save file to C Drive, all appears OK,
except
> the file is not there in explorer
> I open Notepad, type some text and try to save to C Drive, Notepad informs
> me that I do not have permission to save to this location.
> So what I would like to do is something like Notepad, Test if the user has
> permission to write a file to the selected location and if not then
suggest
> an alternative, rather than how word 2002 and my prog does it.
>

I understood the basic idea. I was just wondering
about what sort of scenario would require a person
running as a normal user to care whether the file is
*really* at C:\file.txt, since they can't access the disk
anyway. I'm assuming that when they go to look for
the file again Windows will show them a dummy C
drive in the File Open dialogue, which is really a folder
hierarchy inside their personal folder, and their file
C:\file.txt will be there. (It would certainly be very
confusing if Windows redirects the file save but then
allows access to the real C:\ directory.)


From: Dee Earley on 4 Mar 2010 04:11
On 03/03/2010 18:20, mayayana wrote:
>> Take these two examples to explain my question
>> Using MS Word 2002 on Windows 7
>> I open word, type some text and save file to C Drive, all appears OK,
> except
>> the file is not there in explorer
>> I open Notepad, type some text and try to save to C Drive, Notepad informs
>> me that I do not have permission to save to this location.
>> So what I would like to do is something like Notepad, Test if the user has
>> permission to write a file to the selected location and if not then
> suggest
>> an alternative, rather than how word 2002 and my prog does it.
>>
>
> I understood the basic idea. I was just wondering
> about what sort of scenario would require a person
> running as a normal user to care whether the file is
> *really* at C:\file.txt, since they can't access the disk
> anyway. I'm assuming that when they go to look for
> the file again Windows will show them a dummy C
> drive in the File Open dialogue, which is really a folder
> hierarchy inside their personal folder, and their file
> C:\file.txt will be there. (It would certainly be very
> confusing if Windows redirects the file save but then
> allows access to the real C:\ directory.)

Yes, file enumeration/access "merges" the two folders for
incompatible^Wnon vista aware apps. All writes go to the virtual
location and override the same file int he real location for that user.

--
Dee Earley (dee.earley(a)icode.co.uk)
i-Catcher Development Team

iCode Systems
First  |  Prev  | 
Pages: 1 2
Prev: VB6 With/End With - how to pass the object itself?
Next: Debugging Tricks : Going Blank