I have added a macro to attach a highlighted section of excel to an email as a pdf.
This was working perfectly in my test workbook. When I tried to add the same macro to my working workbook i got a "Compile Error: User-defined type not defined".
I thought it might have been just on my live workbook, but the attached gets the same issue.
What am I not seeing?
You haven't set a reference to the Outlook object library in that workbook.
Rory
You lost me at "Set a reference". Could you let me know what I need to add/alter to get it to work?
Developer tab > VBA Editor > Tools > References ...
Find the correct object on the list and tick it.
Ali
Enthusiastic self-taught user of MS Excel who's always learning!
Don't forget to say "thank you" in your thread to anyone who has offered you help.
You can reward them by clicking on * Add Reputation below their user name on the left, if you wish.
Forum Rules (updated August 2023): please read them here.
Hello again Ali
I did that when I originally set up the macro.
AND I have just seen the reason it didn't work, I allocated the MS Office, not the MS Outlook reference, but I do not see how/why it would work in the first instance, then not.
I am having a further issue with the same macro.
The end of the script should delete the temp PDF. I am happy to remove this bit of code as ideally I want the PDFs to be saved as well as emailed, so not deleting is a bit of a blessing in disguise.
But, for my own sanity, can someone explain why the Permission Denied error appears?
Because there are separate objects for each of the Office components (Word, Excel, Outlook, etc.). I learnt this when I was merging data from Excel into Word via VBA.but I do not see how/why it would work in the first instance, then not.
Yep, I fully get that now. But I cannot fathom why it would work initially with "Office" applied, but then 'break', but work when "Outlook" was added.Originally Posted by AliGW
but it is working, which is a god-send.
Thank you.
I don't know the answer to that, but if the object wasn't selected, then the call on it would fail. Something else may have been the cause.
You said you moved the code from one workbook to another. The reference is stored with the workbook, not the code, so I suspect that initially you had correctly added the outlook reference to your test workbook. The Office reference is selected by default.
Your code is using late binding, so change Dim statement
to
Please Login or Register to view this content.
So that no need to set the reference.Please Login or Register to view this content.
That is early binding, since the variables are declared as specific types, not Object. Your suggested changes would make it late binding.Your code is using late binding, so change Dim statement
Please Login or Register to view this content.(using CreateObject does not determine the binding context)
You need to read the code in the workbook uploaded.
Please Login or Register to view this content.
I've read the code. It contains this:
and that is early binding. As I said, using CreateObject does not determine binding context; only the variable declaration does that.Please Login or Register to view this content.
But it is not actually early binding unless set the reference.
Anyway it should work.
There are currently 1 users browsing this thread. (0 members and 1 guests)
Posting Permissions
LinkBack URL
About LinkBacks
Register To Reply
Bookmarks