🚀 go-pugleaf

"Randel Bjorkquist" <rbjorkquist@coilcraft.com> wrote in message
news:40b4d96f@newsgroups.borland.com...

> I am retrieving the file and letting windows open it with its
> associated program.  So if I change it, I'm not sure how to
> open the file so the end-user can see it.

Rather than using ShellExecute(), you could use FindExecutable() with the
original filename, and then use CreateProcess() to run the program directly,
passing it the temporary filename.  Then it (usually) doesn't matter what
the filename actually is.  Or, you can just look in the Registry directly to
determine how a given file extension should be loaded (you can use my
TRegExtension component for that: http://reg.lebeausoftware.org).

> I guess I was being lazy by trying to let Windows clean it up without
> having to write something to do it.

I suggest you read the following article, it explains how to work with the
Disk Cleanup utility:

    Creating a Disk Cleanup Handler

http://msdn.microsoft.com/library/en-us/shellcc/platform/shell/programmersguide/shell_int/shell_int_extending/disk_cleanup.asp

    "The basic challenge inherent in disk cleanup is to free as much disk
space as possible without deleting essential files. Because there is no
standard way to mark files for cleanup, no single application can reliably
detect and clean all unessential files. The Disk Cleanup utility addresses
this problem by splitting the cleanup operation between a single disk
cleanup manager and a collection of disk cleanup handlers."


Gambit