The key to the entire thing here is that if YOU want to judge the file as
corrupt then YOU have to be bale to read the file in the same way that the
target application would and then make a judgment of fitness or not.
If you want to know if a word doc if valid or corrupt before you try to open
it in MS Word then you have to open the file, understand the MS Word
document structure and be bale to know if the file is corrupt or not. This
seems like an awful lot of work especially if you intend on opening many
different file types.
Perhaps you might want to consider a third party imaging toolkit like this:
http://www.leadtools.co.uk/
NOTE: A do not work for them nor am I connected to them in any way. I just
see their add allot in the back of VBPJ.
"vinay" <vk******@fcg.com> wrote in message
news:F7**********************************@microsof t.com...
Thanks a lot for your interest and suggestion. But my application might
further extend to support PDF files, Bitmap files, In such a case I want to
know whether the file which is being opened is corrupted or not before
actually passing the control to the respective application reader. As the
type of file which is supported by application might differ in future, I am
thinking of using Systen.Diagnostic.Process class. Please help me in this
regard.