That's not the answer. Whether the file is incorrectly referenced in the pz2, pz3, cr2 or whatever, isn't the point. There is no excuse/reason/mandate of God that could excuse the sloppy code writing that allows a misrosecond response from the operating system and five lines of code to handle to take ten minutes and lock up the system in the process. THIS FILE LOOKUP PROBLEM MUST BE FIXED. For COBOL's sake, just delete the damn file search routine entirely and stop at "File Not Found", dump to a dialog and ask what to do,... then frikkin' do it!! Its amazing to me that I can click "Stop looking for files" and it still takes ten minutes to understand the response,.. incompetent code writing,... evil, pure and simple, from the eighth dimension!!