I think I'm going to start ignoring SO questions that refer to VBA as a "script" in the title. If I wanted to look at that, I'd follow the [batch-file] tag.
@Inarion Settings.settings is a designer for App.config
VS is [supposed to] keep them in sync
also...
@MathieuGuindon I didn't understand what you tried to say, but I just realized that my note about overloading has nothing to do with the question. )) — JohnyL18 mins ago
> @retailcoder : > The assembly pubic key tokens aren't sensitive at all, they're just public IDs for known assemblies, namely Office.dll v12.0 in this case (key tokens are identical for that assembly, on every machine in the world)
Haha, thanks for pointing that out. Old habit dies hard I guess; we're a little overly security conscious at my work.
@bclothier :
> 1. Was the workbook read-only, or on a read-only media?
> No, I am not. However, I might be able to persuade those that are in that position (as a last resort). Fortunately, MZ-Tools loads (both at start-up and manually) and runs normally.
> No, I am not. However, I might be able to persuade those that are in that position (as a last resort). Fortunately, MZ-Tools loads (both at start-up and manually) and runs just fine.
i find it puzzling because that does not jive with my early experience of VSTO - it was embedding interop which also mean that it would blow up on a different version of Office, and required a new set of PIA to be shipped just to enable users to use a new version.
@this And even 2000. I guess it's because the DispIds don't differ. Certain properties can't be called in early Office \ VB6, hence the missing toolbar icons in those.
(and that might be also relevant to the poor sod's issue - I don't know if PIA will behave similarly to VBA reference in that if a newer version it will automatically forward to that version)
So, whenever I open anything, I get an error message that the reference to Word 16 was missing.
IIRC, we repeatedly got issues with RD breaking for people that had multiple office versions installed on their system over time, probably in the wrong order.
Is it possible when an addin assembled/compiled from a newer verison conflicts when running with an older verison like 2010? Was thinking along the lines that I downloaded PowerPivot so it could work in 2010.
Hm, testing whether the MissingAttributeInspection works for Exposed and PredeclaredIdis probably pointless, but I will do it for the sake of completeness.
Btw, do we use the IgnoreModule annotation to ignore something everywhere in a module?
VBA Rubberducking
VBA Rubberducking