Sorry. Forgot to say, debug aids were put in to call fflush() - no failures found - then removed.
Sorry. Forgot to say, debug aids were put in to call fflush() - no failures found - then removed.
Never re-write code unless the user benefits
>> Win7 PC's on a 2003 network do not exhibit this problem.
I was under the impression that the issue occurs when writing to a local drive - no networking involved.
Does the issue occur on a local hard drive, flash drive, or network drive?
gg
The issue occurs on a local drive, that's correct, but the Windows 7 PC has to be connected to the network for the problem to arise in the combinations described.
all of our software is multiuser and client server, and all application programs reside on the server, or a singler PC on the network in peer to peer configuration.
The only time files are written to local drives is for external machine control for machines that are incapable of being networked.
Normally, files are written to removable media, which is when the problem first arose. However, the first workaround - writing first to the C-drive and then file copied to a removable device failed because the original copy on the C-drive corrupted as per the removable drive. This eliminated removable drives as the problem.
I think I have already mentioned that if the file is written to a network server, there is no corruption.
This means that whatever is amiss is on the Windows 7 PC itself.
As you can appreciate, the only data difference is the file name is now X:FRED instead of C:FRED.
Never re-write code unless the user benefits
