>Tamar,
>
>I've had this happen with the pack command when removing records after a small batch posting. It started after the clients network guys upgraded and few things and put some backup / drive replication processes on the machine. After checking for other users accessing the file I determined that some other system level process had it's hooks into the thing. Working with the IT guys, they confirmed that they're shadow-copying the drive periodically and have a mozy-pro offisite backup process running as well. When I had them temporarily exclude our system data folder, the problems stopped.
>
>Both of those processes are beneficial, so I wrapped the pack in a try-catch block to "nerf" the error and log success/failure. After re-instating the other processes, I found that the system failed to pack only 1 out of 38 attempts. It's been running along fine ever since, packing the file whenever it can.
>
>One thing to note though - when it did "fail" it was corrupting the associated index more times than not. Something to look out for.
>
>I hope that gives you some idea of other things to look for (I can't count the number of times I've benefited from your ideas <g>)

Yes, some ideas here.

Thanks,
Tamar