Improve the Visual Basic Development Environment to be similar to Visual Studio
When working in Visual Studio the VBA VBE seems so primitive. See the features here
The features in the Visual Studio text editor make writing, navigating, and debugging code so much simple:
The Visual Studio editor provides many features that make it easier for you to write and manage your code. You can expand and collapse different blocks of code by using outlining. You can learn more about the code you are using by using IntelliSense, the Object Browser, and the Call Hierarchy. You can navigate inside your code by using features such as Navigate To, Go To Definition, and Find All References. You can insert blocks of code with code snippets, and you can generate code by using features such as Generate From Usage. If you have never used the Visual Studio 2015 editor before, see Editing Your Code for a quick overview.
You can view your code in a number of different ways. To see a class view of your solution, you can open the Class View window or expand the nodes in the Solution Explorer under your class files.
You can search and replace text for single or multiple files. For more information, see Finding and Replacing Text.
Thanks for weighing in on this.
VBA is very important to us, and we’ll continue to add object model for new features (see http://dev.office.com/blogs/VBA-improvements-in-Office-2016), so you have programmable access to all of the capabilities of the application.
However, changes to VBA are driven cross Office apps and not directly by Access team, so I’m declining this request so you can re-use your votes.
Feel free to follow the developer blog http://dev.office.com/blogs, where we’ll communicate changes to VBA.
James Lee commented
Comment on an idea about VBA IDE that's under review at https://officespdev.uservoice.com/forums/224641-feature-requests-and-feedback/suggestions/15446658-give-the-vba-ide-a-major-overhaul-finally
Heinz Hoegel commented
I am very disappointed with the attitude of MS in this matter. Here a so-called strategic alignment is used as an excuse not to eliminate an existing shortage for many years. The ongoing reality for the vast majority of developers in the MS Office environment (and base of their daily work) is simply ignored!
Raimund Popp commented
will the vba-editor for office be improved somewhen? (link)
Dick Watson commented
I'm with Mark Burns. As much as I'd like to see it, it's just so much bigger than Access and clearly highly unlikely to happen because Microsoft's strategic direction for serious Office development is NOT VBA. Unless you have votes to waste, this probably isn't worth voting up.
Mark Burns commented
i AM REMOVING MY VOTE FROM THIS - Not because I don't want this to happen - I am extremely of the opposite mindset! However, from the other feedback MS has shared in the Excel uservoice site on this very same request for VBA improvements (which had many more votes than you see here), MS is definitively NOT going to do anything like this. Ergo, I am moving my vote to greener pastures. I recommend you do the same. For the record There were 60 votes for this when i retracted my vote.
Raimund Popp commented
the actual status of the vba programming became so obsolete that it is a shame for me. since the beginning of 1994 on access 1.0, nearly nothing changed in the vba programming engine. meanwhile the access programmers have the appearance of old men on a dying system.
Jack Leach commented
Absolutely, even little things like "Create Method Stub" or Code Peek (though code peek would be difficult due to the MDI rather than WPF IDE base). In any case, there's tons of improvements that could be made to the VBIDE to help with developer productivity.