Jump to content
Claris Engage 2025 - March 25-26 Austin Texas ×

This topic is 6427 days old. Please don't post here. Open a new topic instead.

Recommended Posts

Posted

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

This topic is 6427 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.