$$*.MPX and e-mail PDF's

[Raymond Lyons]

I don't know about anyone else but those pesky MPX temp files are no longer being deleted from the Windows temp folder, and once in a great while a few are showing up in ADB folders.

Additionally, I have found that if one uses A5's option to send a report via e-mail, at least using something other than the A5 e-mail client, that the PDF�s stay in the Windows temp folder forever unless one cleans them out. This is particularly troublesome because each time you send the same report name, it does not merely overwrite the old name in the temp folder. Rather the new one gets a new incremented name such as report2, report3 and so on. Unlike most MPX files the PDF�s can take up a lot of disk space quickly if one does a lot of e-mailed reports.

In any case, I have dusted off and modified an old Cal Locklin script (thanks again Cal) to delete these pesky things until Alpha addresses the issue. Be careful, though, this modification of Cal�s original script may or may not be exactly what you may want. Examine it and use at your own risk. I have tested it but I have yet to put it into production in a user environment. Also note that you can also end up with the PDF files sticking around in the attachment folder used by your e-mail client. That is not addressed in the attached script.

Ray Lyons

[CALocklin]

RE: $$*.MPX and e-mail PDF's

Thanks Ray. I've been thinking about that PDF issue lately myself - now I have a ready made solution!

[However, my ultimate solution in this case (e-mailing invoices) will be the creation of a button to save the report the report with the invoice number in the name so it makes more sense to the recipient and allow the user to save it in a different folder. If not saved, the routine will either delete it after it is sent (this may be difficult) or maybe a routine will be added that deletes all Invoice*.pdf files in the temp folder before another one is printed.]

Cal Locklin
www.aimsdc.net

[Raymond Lyons]

RE: $$*.MPX and e-mail PDF's

Cal,

Attached is an arguably somwhat better solution, mostly from the MAN. I have every reason to believe that some if not all of this will be addressed in an upcoming patch. For your special purposes you'll still have to roll your own though. I hope you can see your way to sharing whatever you come up with.

Ray

[CALocklin]

RE: $$*.MPX and e-mail PDF's

Thanks Ray - and Selwyn, of course.

This is another example of "gotta remember to update scripts." Too often I forget about the new functions when updating existing scripts.

[Lenny Forziati]

RE: $$*.MPX and e-mail PDF's

Ray, in your first script, your comments say this doesn't work well as a function in the autoexec because it takes too long. While your second version should be faster, here is a framework for a function that will create a background thread to do the work at the lowest priority. The result is a non-blocking function that returns essentially instantly, making it safe for use in your autoexec.

This won't work in V5 though, threads are a V6 feature.


function RaysCleanup as v ()
thread_create(thread_name_create("Ray's cleanup"),""%code%
dim self as p
self = thread.current()
self.set_priority(-2)
'your code here
%code%)
end function

[Raymond Lyons]

RE: $$*.MPX and e-mail PDF's

Thanks Lenny. The comments were actually Cal's and it started out life as v4 script I believe.

I presume that my second script (99% Selwyn's except for any imperfection, which is wholly mine) will work in your code. I don't see why it wouldn't.

As an aside on the PDF's, I just got an e-mail from a client this morning re: 200+ PDFs in one of his Windows Temp folders. Prior to last week I didn't even know they were going there. I assume a patch will be addressing these issue? Or not?

Ray

[Lenny Forziati]

RE: $$*.MPX and e-mail PDF's

Yes, my code will work with Selwyn's as well. It will work with any non-visual code But it you try to do anything with the UI (ui_msg_box(), debug(), etc), Alpha Five will freeze

I do not know about a patch. Selwyn appears to be aware of the issue since he helped you with the script, so I would imagine he'll address it.

[Raymond Lyons]

RE: $$*.MPX and e-mail PDF's

Just thought I should let everyone know that Selwyn's code snippets (in my 2nd attached file) put into Lenny's thread function works like a champ. I put the function in my autoexec script and can see no speed difference at all (being a thread, I suppose that is to be expected). Particulary with the e-mailed PDF's this can be a significant issue. I had thousands of undeleted files in my windows temp folder taking up many MB's of space.

Ray

[Jerry Gray]

RE: $$*.MPX and e-mail PDF's

Ray,

Would you want to run this in the autoexec or in an exit routine?

Either way, thanks for the headsup.

Jerry Gray

[Raymond Lyons]

RE: $$*.MPX and e-mail PDF's

Jerry,

I thought about this before I put mine in the autoexec but could not come up with a real good reason to prefer an exit routine. I suppose one could even put it in both places.

It is very fast, so another question is more on the theoretical side: Can one of these v6 threads even finish their job after A5 closes? I kind of doubt it but it would be good to know. Lenny?

Ray

[Jerry Gray]

RE: $$*.MPX and e-mail PDF's

Ray,

I was just thinking about it from a security standpoint. The PDF files can be read by anyone with access to that drive. To close as many loop holes as possible, I think it would be best to clean up after the report processing instead of before. Some data might even warrant running the process at the end of the report.

Jerry