>> >No, but you do need some sort of access to one. Assuming you're using
>> >NT, have a look for a program called BLAT. It does a Wonderful job.
>>
>> Do you have a list of the error codes that BLAT returns? I am using the
>> WinExec function from Win32API.
>
>I've generally just used the return code from WinExec(). If the type is
>"N" (for some reason, this isn't always the case) or the value is <= 32,
>then I write the message to a file.

I think I figured out why I was getting large numbers for my return codes. It seems if I run BLAT on Windows 95, I get the large numbers. When I run it on Windows NT, I get small numbers. These small numbers correspond to the return values found in BLAT.cpp. I'm not sure why the numbers on Windows 95 varied even for the same BLAT call.

Anyway, I discovered that an error occurs in BLAT when its return code is not zero. For example, a return code of two means that the file passed to BLAT does not exist. I would be interested to know whether anyone has been able to obtain the correct error codes from Windows 95.

Thanks for your help and for mentioning BLAT!