Hi Cindy,

UPDATE: I neglected to mention that this really depends also on the server os. Closing open files has gotten better with newer OS's. For instance, in W2k server you have the option to disconnect or to close all open files or both. This is done at the OS level so you data would be lost, but the file should not typically get corrupted. However, since the messages that are sent to the user when both of these options occur can be customized, it is difficult to tell which or if both are occuring. Since this is done at the server level, once the actual disconnect occurs with the client, the message that the client machine itself displays can also be misleading because the client can sometimes only realize that the disconnect occurred, but not what the condition of the file is or how it came to be closed (safely or unsafely). I guess what I am saying is that there is a lot of variables here and we do not know by what means your network folks are closing files and disconnecting users or if they are running 3rd party software on the server to do this also.

ORIGINAL MESSAGE:

When I worked for the government we had basically the same situation as you describe occuring early on. I was fortunate though in that I was also the network manger at the time and could see it from both viewpoints and attempt to resolve the situation (instead of having someone just tell that 'this is the way it is, period.'-I HATE that) We chose to use Vinca StandbyServer and backed up the standby server which helped tremendously. We also changed our backup times on our servers to 2:30am so we could accomplish it before the breakfast POS came up at 4:00am (it was a military base afterall), but after the bars and bowling centers closed out for the day at 2:00am. However, during this period I did receive training on different backup methods and commercial products and the most common scenario is that the file is not corrupted from being open when backup needs to occur or the connection is lost (although it CAN occur in rare cases), but just not backed up because the backup software or the OS could not get exclusive open of the file to back it up. This depends on the network client that is in use also though (some attempt to reattach repeatably and obtain a temporary file lock-which may cause problems-when disconnects occur) and can be different depending on the configuration in place. Additionally, this also happens sometimes with over-agressive anti-virus software running on servers also. I have documentation (hard) on backing up open files and disconnecting while files are open, but I believe that some of the information is also available on websites. Also, new technology can change things and I am not as up-to-date on it all as I once was. However, when I get home, I will check my documentation and see if it can be located from their website as well so you can get the information in writing or least get someplace to start.