I still don't get what it is you think is caching the file. Why not
just delete the PDF as soon as you have emailed it?
-dhs
--
Dean H. Saxe
[EMAIL PROTECTED]
On Nov 8, 2008, at 9:52 AM, [EMAIL PROTECTED] wrote:
Sounds like my original response. Check for the file first...
Sent via BlackBerry by AT&T
From: "Howard Fore" <[EMAIL PROTECTED]>
Date: Sat, 8 Nov 2008 09:19:22 -0500
To: <discussion@acfug.org>
Subject: Re: [ACFUG Discuss] Another CFMAIL Problem
Why not go ahead and use the job number, but when you're about to
write the PDF to disk first check to see if there's already one with
that name (initials and job number). If you find one then delete it,
then create the new one. Is there some audit reason to keep the
earlier version?
On Fri, Nov 7, 2008 at 3:48 PM, Peyton Todd
<[EMAIL PROTECTED]> wrote:
One solution I thought of is simply to use the job number as the
name of the PDF. This would guarantee that each next one built is
different. But then it occurred to me that if the user reports a
job, then realizes he made a mistake, corrects it, and sends the
report again for the same job, there's a danger that the earlier
mistaken version would get sent instead.
--
Howard Fore, [EMAIL PROTECTED]
"The universe tends toward maximum irony. Don't push it." - Jeff
Atwood
-------------------------------------------------------------
To unsubscribe from this list, manage your profile @
http://www.acfug.org?fa=login.edituserform
For more info, see http://www.acfug.org/mailinglists
Archive @ http://www.mail-archive.com/discussion%40acfug.org/
List hosted by FusionLink
-------------------------------------------------------------
