Some videos you may like
The behavior that Microsoft built into the list you describe is not able to be manipulated in the VBE such that it is viewable all the time.
As I wrote in my last post, that pop-up list is only viewable when the code context is conducive, and the afore-posted settings are established.
Share it with others Like this thread? Page 1 of 2 1 2 Last Jump to page: Results 1 to 10 of Run Intellisense constantly in VBA. Thread Tools Show Printable Version. Strange, I have every box checked, but still the list disappears after every witten line. Maybe you are expecting to see the list during times when Intellisense is not bound to be active. Thanks Tom, I think I know what you mean. Based on how I read your posts, my understanding of Intellisense is that your expectation of when you'd see pop-ups exceeds when pop-ups are meant to occur, considering how Microsoft built the Intellisense feature into Excel.
Ah, I think I have mistaken what Intellisense actually is. You do realise that you are responding to a thread from ? All times are GMT The time now is Resources saved on this page: Hope that makes sense Rdster 1, 7 But for built-in classes, it's "nope". I can now run classes via the Immediate window, wow.
I have this empty StaticClass. I usually keep those for factory methods. The answer is a plain and simple No No. Therefore, the way you wrote your code is the correct way to do it. I was afraid of that. Rdster yes, that's unfortunate and we all wish there was more to the language than that. H Jan 24 '17 at Perhaps easier to just assign to a variable, but here is one approach: In order to fully qualify this though, you'd need to use Activeworkbook. In this specific example, you don't need to qualify it as it is the active workbook, but I agree that in general this approach is a bit of a dead end.
Sheets 1 'Yet more stuff Done End With. In reply to NFL1's post on September 11, Thank you for responding: There's very little in the way of properties for Form control buttons. Basically you have the click event which runs the macro you assign.
The first button you create will be called "Button 1". If it's actually called Button 1, then my code works fine. Thanks for marking this as the answer. How satisfied are you with this reply? Thanks for your feedback, it helps us improve the site.