I have some stores that use a vendor for their systems installation, maintenance, and backups. The systems tech tell me that he provides the security of backups every twenty minutes using an imageserver. I think this is all done with some version of Microsoft's Window Server product or Windows 2000 running on a server with XP on the workstations. Recently, I have noticed that some of the data that was in the transaction files for an accounting program at the end of the month closing, is no longer there. Parts of the software archives copies of invoices and customer histories which still show the transaction items that should be stored in the transaction file. However, somewhat random number of invoices that once were in the transaction records in a transaction file that is supposed to have the transactions in it, now has the dropped records. The software has been in use for ten years and has never had this kind of problem before beginning the imageserver work. My question is this: Can a correct copy of a file be made during a backup using the imageserver process if during that process the file has some records in use and therefore locked while the file to which they belong is somehow copied by the imageserver process ( whatever that is). How can an image server backup data which is at the time of the backup being used to make changes to a record in a specific file. I know that the file record being created will not allow the software to be copied or written over when the system thinks the file is open. I wuld just like an idea of whether there is know-how that can permit a backup under these circumstances which avoids the following scenario. 1. A file is open, one of its records is selected and modied by recording a payment to a previously recorded invoice record. That part of the file is off in memory being modified to show the latest data. In the interim, an imageserver does it periodic backup. I suspect this would cause an acces fault or would just copy the data in the file at the time the backup routine hits that particular file. After the backup, the changes are then written to the file which makes it different from what was backup. Finally, the scenario predicts that restoring a backup made under these conditions would result in the restoration of data which was copied in to the backup before the change in the active record was stored back in the file. Could this be how it works in the imageserver model? I would like to know that my suspicion is incorrect and that the system can be correctly backed regardsless of the changes being made to the files during the imageserver backup.