Visual Basic for Applications or Visual Studio, what are the distinctions between them?
Visual Basic for Applications or Visual Studio, what are the distinctions between them?
I'm facing difficulties with Microsoft on this matter. My PC has Office 2016 Pro installed, and I use macros on a regular basis. A spreadsheet was downloaded from a trusted source, but the person who wrote the code mentioned using Office 365. When I tried to run his macros, I encountered a compile error: Can't find project or library. I attempted to update the Visual Basic for Applications, but discovered that VBA isn't installed at all. I verified the VBA permissions in the Trust Center, and checked the directory they indicated, but there was no VBA folder—VBA isn't present on my system. Updating the VBA version was impossible because the update process couldn't detect the presence of VBA.
My questions are twofold:
1) I downloaded Visual Studio expecting it to provide the necessary files for activating VBA, but it didn't work. I need to clarify the distinction between VS and VBA.
2) Where can I obtain a standard VBA program? From my research, it should be included in the Office 2016 Pro download. I ran the repair/modify option in Apps & Features, yet VBA remains absent from my PC.
Help Please!
VBA is a language integrated into the Office suite. It doesn't exist as a standalone program; Office itself contains VBA capabilities.
Visual Studio serves as a platform for developing code, including VBA and other languages.
Office365 and Office 2016 have slight differences. For O365-generated content, your Office 2016 installation might lack the necessary libraries to execute that macro.
You'll need an office to 365 to operate, likely due to missing a required library it relies on
Would it be possible to insert the image you saved in your pictures file for the screenshot? Downloading it seems like a lot of effort.
The definition of "fullpath" is not specified in the provided context. It is unclear whether it is set elsewhere or if it needs to be verified.
Yes, he mentioned writing it in and using Office 365 to execute the macro. He believes it's likely a legacy problem and thinks I might need Office 365 to fix it. Is there a particular question you should ask him?
I discovered that Shockwave Flash is no longer supported, but there are ways to resolve the compilation problem now.