Microsft Outlook Objects

[Lou_Reed]

I am writing some VBA code to send an email using MS Access 2010 through MS Outlook 2010.

In the tutorial that I have seen it says you must activate Microsoft Outlook Objects (Tools then References).

I have done that on MS Access 2010, but it is version 14.0. I need to know is that adequate correct for this
version of MS Access 2010.

Also when does this have to be done? I have already written the code to send the email and thus would have to load
Microsoft Outlook Objects after the fact (the code is already written).

Any help appreciated. Thanks in advance.


Respectfully,


Lou Reed

[Bulzie]

Add the reference to it, in a code window on any form, go to Tools, References and scroll down the list to find the Microsoft Outlook Objects reference and select it. Save then still in the code window do a Compile to see if you have any issues. Test your email and see if it works. I would make a backup copy of the database before doing these changes incase you need an easy way back if things mess up.

[Lou_Reed]

Thanks I will give it a try.

Respectfully,

Lou Reed

[Lou_Reed]

I have nit got the email ready to test so I am wondering if there is another way that I can test to see if Microsoft Outlook Objects is loaded.

Any help appreciated. Thanks in advance.

Respectfully,

Lou Reed

[Bulzie]

In the References list, if it is checked with no "Missing:" text then it is good. But you need to do a test to verify it will work as you want. Just do an email to yourself with hardcoded values to test.

[Lou_Reed]

What are the consequences if this does not correctly load?

I mean exactly what would I see on the screen if it incorrectly loads or fails to load?

Thanks in advance.

Respectfully,


Lou Reed

[Bulzie]

In the code window, do Debug and Compile and see if it gives an error or not. If no errors then you might be good to go.

[Lou_Reed]

Well, I am ahead of you there. That is exactly what I have done. It gags on certain lines such as

Me.Attachments = file

or

Me.txtBody

Me.txtSubject

Me.txtTo

me.Attachments = Null


I am not sure, why they fail, that is just a sampling. I am trying to

upload a *.png screen of all the lines that compile fails on and that

has not been easy or direct uploading a *.zip file.

I have a separate post on it.


Any help appreciated.


Respectfully,

Lou Reed

[Bulzie]

Me.Attachments = file
Is file the variable that has the patth to the file you want to attach? May need to put the actual path there.


Are the fields on your form called txtBody, txtSubject, etc.? Are you calling this code from the form that has those fields? If not the Me. won't work, you will need the full path of the form they are on like Forms!frmMain!frmEmail!txtBody

Me.txtBody

Me.txtSubject

Me.txtTo

me.Attachments = Null

[Lou_Reed]

I have uploaded a zipped file (correctly this time) of the errors that occur when I try to compile the
VBA code.

I am almost certain it is some systemic issue because off the similarity of the errors.

This is simply a screenshot of the code after I click the dropdown menu and then clicked compile.

I will check the options that you enumerated in the previous post.

Any help appreciated. Thanks in advance.

Respectfully,

Lou Reed

[Bulzie]

Not sure where to help you with this, maybe others can help direct you with your code. Can you take a screenshot of your References box and paste it in here? So you cannot even get your code to run it bombs out on the compile?

What about just using a simple SendObject line but with an attachment?

DoCmd.SendObject acSendTable, "Employees", acFormatXLS, _
"Nancy Davolio; Andrew Fuller", "Joan Weber", , _
"Current Spreadsheet of Employees", , False

https://msdn.microsoft.com/en-us/lib...ffice.12).aspx

Or maybe check out some email examples in the Code library:

https://www.accessforums.net/showthread.php?t=41579

[Lou_Reed]

On post number 9, you have the line

me.Attachments = Null


There is an extra s on me.Attachments. I assume there was a reason for this.

I tried the code as you suggested. No luck.

So now me.Attachments = Null and me.Attachment = Null

neither work. I am not sure why

me.Attachment works in a earlier subprogram without the s.

What was the reason for the original line that you typed?

Any help appreciated. Thanks in advance.

Respectfully,

Lou Reed

[John_G]

You may have hit one of those times where Access does not like Me.txtControlName. Because you have the period in the reference, it thinks you are referring to a form property which doesn't exist, so you get an error. Try changing all your form control references to Me!txtControlName (using the !) to see if that helps.

[Lou_Reed]

You may have hit one of those times where Access does not like Me.txtControlName. Because you have the period in the reference, it thinks you are referring to a form property which doesn't exist, so you get an error.  Try changing all your form control references to Me!txtControlName (using the !) to see if that helps.

Please explain in more detail this statement. It went right over my head.

Thanks in advance.

Respectfully,

Lou Reed

[Bulzie]

On post number 9, you have the line

me.Attachments = Null

That is what you posted above, that is not my lines. Look at your post #8. Honestly I think you should ditch your code and use the one from the link I provided as that one should work. Also take a snapshot of your Reference list of dlls and post it here. Did you ever check the reference for the Microsoft Outlook Objects (Tools then References)?