CDO Replacement for .CreateMHTMLBody

<< I cannot delete the temporary html file until I exit Access>>

  Are you closing the file?  How are you creating it?

JimD

 and yes, you can certainly send HTML through CDO without that.  All you need is the HTML in a string:

http://support.microsoft.com/kb/286431

JimD.

Thanks as always.

I am creating the file using the following syntax:

Dim strHTMLFilename As String
strHTMLFilename = "D:\Test.html"
Open strHTMLFilename For Output As #1
Print #1, varHTMLBody       'This is the variable containing the full html script
Close #1

At this point I can still delete the Test.html file.  However, once I have run the following method:

.CreateMHTMLBody (strHTMLFilename)

The file appears to stay open.  All of the variables are cleaned down at the end (and are only local variables).

**************************

I used to use the .HTMLbody method, but it caused formatting issues when sending graphical emails to certain platforms (mac, iPhone, Web Office) etc.  As soon as I moved to the  .CreateMHTMLBody("D:\Test.html") syntax - everything looks correct on those platforms.

That's pretty much the route I've gone down (multiple files).

Just in case it's me...After the .send command has been issued, I simply have the following command to clean up:

set objMessage = nothing

(objMessage is the objct variable used).

  Do you also .Logoff the session and set it to nothing?

JimD.

.Logoff - uhmm, never used that.  Is it something that should be put after the .send command?

<<.Logoff - uhmm, never used that.  Is it something that should be put after the .send command? >>

  Yes, but it applies to the session object, not the message object.

JimD.

Thank JimD,

I'll assign the points to you in a mo, but how/where is it used?

Here's a link to MSDN on sending with CDO:

Creating and Sending a Message
http://msdn.microsoft.com/en-us/library/ms528126(v=EXCHG.10).aspx

 Which has sample code showing it's use.

  I've only used CDO a couple of times in the past and don't remember using the .Logoff either, so I don't know that it will solve the problem.

  Not sure what your code looks like, but something is not getting released (and it may be some type of bug).  I know the .Send method is supposed to invalidate the message object, so the only thing left is the session itself.

  But with that said, I would have thought that .Send would have completed anything to do with the Message object, so it doesn't make sense.  But I can't think of anything else to try.

JimD.

JimD - Thank you as ever for your help.  In the end I create individual html files, which are cleaned down when the app loads up.

That said, I'm going to take a deeper look into it (when I have a spare hour or two), so will come back if I find anything different.

Thanks again.

What I do is load the contents of the HTML file into a variable. The I assign the contents of the variable to the HTMLBody. This avoids CDO from attaching to the file.

Oops ... Question closed.

No worries and thanks for your input.

In case you are interested, the HTMLBody method seems to cause formatting issues (especially on mac and web-based platforms) when using graphics.  Whereas the .CreateMHTMLBody(D:\test.html) - sorts it all out.  I will eventually find out why this is - but at the moment it just seems like Witchcraft.

Thanks again.

Interesting.   Thanks for sharing that information.  If I figure out anything helpful I will post it here.

Best of luck.

I found that the Accepted Solution didn't work. The CDO object simply didn't let go of the input file until exiting the entire running application. Releasing the form, setting the html source file to null, releasing the CDO object, running the bodyparts.deleteall() or clearstream functions etc didnt' help. Creating mutliple files doesn't solve the situation because then you'd have to persistently store those file names and then after you exit and restart the application retrieve the list and delete the files!

However, I found a *real* solution:
Instead of using syntax: CreateMHTMLBody ("D:\FILE1.HTM") use
CreateMHTMLBody ("file://D:\FILE1.HTM")    or CreateMHTMLBody ("file://D:/FILE1.HTM")    

With this approach releases the lock on the input file immediately.

Phew!

 Many thanks for posting that back to the thread.

JimD.

That's really useful to know - thanks for the post - much appreciated.