Re: Write Access Error When Using CFileDialog
- From: Joseph M. Newcomer <newcomer@xxxxxxxxxxxx>
- Date: Tue, 11 Jul 2006 22:11:38 -0400
Note that the task manager only describes the instances of the program running on the
machine on which the task manager is running. If you have a copy running on another
machine, you get the same error, but you don't get anything from the task manager. At my
site, where I have nine machines in various states (a Win2K machine, a Server 2003
machine, some XP machines), this often happens to me when I do "cross-platform" testing.
Then my problem is to figure out which machine I left a running copy on.
If you're using the process explorer from www.sysinternals.com, search for a handle for
your .exe file on the machine which holds the disk structure on which the .exe file lives,
for example, if you are building to a server, it would be meaningful to do this only on
your server.
joe
On 11 Jul 2006 10:58:08 -0700, "Jon" <TheFakeJon@xxxxxxxxx> wrote:
Thanks, but what process viewer tool? I ran the task manager andJoseph M. Newcomer [MVP]
couldn't find any occurances of my .exe file. For a more in-depth
look, I also ran "process explorer" which is like task manager on
steriods and still no luck. :(
Thanks
Mark F. wrote:
Sleepster wrote:
LINK : fatal error LNK1168: cannot open ../../../bin/myfile.exe for
writing
I don't think the code you posted is the problem. The linker error is probably
telling you that the app is still running and therefore the .exe file cannot be
written because of an open file access violation. Run the proccess viewer tool
and see if the app is still alive.
Mark
email: newcomer@xxxxxxxxxxxx
Web: http://www.flounder.com
MVP Tips: http://www.flounder.com/mvp_tips.htm
.
- Prev by Date: Re: Is MSDN wrong? or I made a mistake? about static member function
- Next by Date: Re: transparency in dlg
- Previous by thread: Re: Write Access Error When Using CFileDialog
- Next by thread: Re: Write Access Error When Using CFileDialog
- Index(es):
Relevant Pages
|
Loading