Hi

This is about the 4th office that has hit a problem using our Unload All 
routine that we have been using for a long time.
It appears to hang when we Run the cms.Dat file.  I have some CPU and Memory 
taco mentors on my side bar and they show my computer is working.

They had to go back to a backup 2 days earlier and the only obivious difference 
it the RB3 file went from 29,417,472  to 39,313,664 in 2 days. The RB2 and 4 
files are about the same size.  I watched the files grow during the Load and it 
appears that the RB4 file took a very long time to load (starting size 
128,145,125)  then building the index file took a very long time too.  It stays 
at 90k for over 10 minutes when it started out at 39megs. 

Their computer tech use to be a MS certified tech or something and a very nice 
guy, he said they installed some program that wrote a log file to the root or 
something like that and he thinks that is what messed things up.  He said that 
log file thing is a known issue at MS.

Are there any ideas on what is going on or how I can take care of this?  BTW 
this same office sent me 3 sets of files each one doing something a little 
different.  

Thanks
Marc


Reply via email to