April 18, 200718 yr I have a scripted solution (Developer 7/MAC OSX 10.4) that is gobbling up disk space. It is going through a database building procedure, converting data imported from another application, so is adding records. After processing & adding about 4000 records, it had gobbled up more than 2.5G of disk space - all that was available - and the system locked up trying to recover cache memory with only about 25M left on the hard disk. As soon as I 'Force Quit', there was 2.5G of disk space available. The FM file size itself is only about 16M. The table has 350+fields, many of which are indexed and used during the record adding process. Why does such a thing happen? Am I doing something to cause such a result? Is there any scriptable file/memory maintenance I can do during such a process? TIA
Create an account or sign in to comment