I have a error message for line "Set vbProj = ThisWorkbook.VBProject" Error message is method 'vbproject' of object '_workbook' failed How can I fix it? Thanks for your help.
Hi @Sigma Coding, Thanks for taking the time to put together such a good video. To be able to programmatically add references the "Microsoft Visual Basic for Applications Extensibility" reference/library has to be enabled. How do you enable this reference/library without asking the user to do it manually? Also, the "Trust access to the VBA project object model" option in the "Trust Center Settings" has to be enabled as well. How do you get around this without asking the user to do it manually? Thanks,
Thanks for the great code. Just for your information there are may references with a type of 0 rather than 1. For example, the Solver add-in that come with Excel and the VBIDE have types of 0. I am not sure what makes the difference however. +
Interesting, I never knew that so thank you for sharing. Maybe it has something to do with it being a "out of the package" add-in? That's the only thing I can think of at this point.
Thanks for such awesome stuff. Just wanted to check if GUID, Major, Minor remain same across different PCs, so that, the VBA code becomes fully portable and ready to use on any machine (No need to ask users to check library references) ?
Sir how can solve StrConv object error in VBA when i run the code then will come error "Can't find the Object in library" Please help me know how can solve the error.
Hi. It is fine if you know the library Name and path in your computer. But it is not usable if you prepare tool for somebody else and you do not know exact version. I just need to add Outlook library if it is not there implemented yet. So something more universal would be fine.
You could use the GUID to add it. It would add it automatically then. Also the file path is the same for all systems so you would need to use the more general user path.
You are enable libraries with code to make the user's life easier, nevertheless we would have to enable VB for application extensibility first? That doesn't make sense to me...
Agreed, kind of defeats the purpose if the person is on a different version of Office than you are. However, in that case you could just use late binding instead.