RE: Dave
- From: Parrot <Parrot@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 25 Feb 2009 13:18:03 -0800
To put it bluntly I don't have time to reproduce the code because it involves
bringing together segments of code from all parts of the program. I take the
approach if it works don't fix it. All I can tell you is that I closed
another file that was being processed after the file I was having problems
was being processed. After that I no longer have the problem. What else am
I to conclude? I have a program to finish. I appreciate the help I get from
these forums and if I have to endure arrogant slanders against my abilities
in the process, so be it.
"Dave" wrote:
After spending hours tracing my program I finally figured out that I didn't.
close the stream for another file that I accessed. This other file logic was
enclosed within a 2 deep function within the logic where I was having a
problem accessing the file in question. So by closing the other file in the
other logic section, I was able to access the file that I was being locked
out from. What is confusing is that the file that I was being locked out
from was a different stream from the file I had forgot to close. In summary,
it appears that if you leave any file open you may a problem opening up any
other file in your program. That to me is perplexing but nevertheless I
solved the problem through old fashioned hard work. Some problems are just
too complex to display program code on a forum.
Dave
- Follow-Ups:
- Re: Dave
- From: Peter Duniho
- Re: Dave
- References:
- File cannot be accessed because used by another process
- From: Parrot
- Re: File cannot be accessed because used by another process
- From: Hans Kesting
- Dave
- From: Dave
- File cannot be accessed because used by another process
- Prev by Date: Re: Creating classes from Linq
- Next by Date: Re: Generic classes with an generic interface as a type parameter
- Previous by thread: Dave
- Next by thread: Re: Dave
- Index(es):
Relevant Pages
|