I have an Excel VBA app where I (and 3 or 4 others) read/write to an Excel
file that exists on a local network drive. At random times, the file is
renamed to an extension-less HEX number during the read/write, open/close
process. I am told that this HEX file is a temporary file and that Excel uses
and then renames back to the original file name (under perfect conditions). I
have this app at about a dozen locations around the country. Each location
experiences this problem from time to time. How can a avoid this problem?

Thanks for any insight.

Chris Picklesimer