>3. My older systems write a batch file to the user's boot drive's root directory, that will be called if the system is re-booted during the running of one of my applications. This batch file deletes any temporary files. With Win 95, however, this method is less relizable than it was under 3.1, so I'm im the process of a re-design of the solution. Probably along the lines of checking the temporary files directory for files that were created prior to the current system date/time.

Why not put the batch file into StartUp directory, then delete it OnShitdown?

>Having said this, I think that it's wise to try to get a feel for how many records a day might be added, so that planning for limited disk space can be done in the design phase, rather than as a reaction to a problem.

Exactly - as long as I can remember, we've always measured the document flow's size and calculated for at least double disk space. OK, it was a must with 40M disks, but nowadays nobody can guess what will grow faster, data or disks, so knowing orders of magnitude at design time is surely as essential as it was back then.

p.s. the typo was accidental