That sounds like a great idea; and may relieve my problem. Hopefully I can get it to work on this program, since it's indirectly using the DB_File module via AnyDBM_File. I'm guessing I can wrap this call into a eval(), so if you try to run this code using a different DB file type (other than Berkeley DB) it won't produce an error.

Still very weird how this is topping out at 10 megs instead of say, 2 gigs. I checked to see if this was an account quota issue (it wasn't)