>This has been popping up lately, after running fine for some months. It's treated as an error by the code I got here on UT, where the return should be > 31. When I change the code to allow 31, it seems to run fine. I can't seem to find any useful answer in Win32api Help.
>
>Anyone know what's going on here? George, Ed, maybe?

Hi Bruce,

31 should mean that there's no application associated with the file. If the buffer that's being passed to the function isn't re-initialized, you could be seeing the results from the previous call to the function.

Care to post a sample of what's going on Bruce?