Make VB6 programming part of Office
VBA programming is already part of Office. It's sister language VB6 should become part of the Office family and be updated to the same standard as VBA7.
VB6 should allow compiling to standalone .Exe files, but otherwise it should retain compatibilty with VBA.
There is still a large volume of legacy Visual Basic 6 code that needs supporting.
We want to thank everyone for their comments and votes on this thread. This is not the first time we’ve received this sort of request. We’ve also heard this feedback on the Excel UserVoice forum. You can read our full response at https://excel.uservoice.com/forums/304921-excel-for-windows-desktop-application/suggestions/8843113-bring-vba-into-the-modern-world.
We’ll summarize the key points here.
VBA will still continue to be supported in Office, and as we add new features in the Windows desktop versions of Office, we will add object model APIs for those features. You can find more details about feature improvements here: https://aka.ms/odevblog-vba.
Again, we appreciate the developer passion around VBA, and we’ll continue supporting VBA.
Office Extensibility Team
Lisa K commented
This is a good idea. VB6 programming should be part of Office.
Yes, include VB6 programming in Office. It is almost identical to VBA programming so it makes sense to do this.
John McCluskey commented
Please do this. VB6 is very similar to VBA. It makes sense for the Office group to support and develop both.
I would like this very much. But you must keep VBA programming in Office, not simply replace it with VB6 programming. Both are very similar but have different uses.
I used to be opposed to VB6 but I now think it is a good idea to add VB6 programming to Office, in addition to VBA programming.
Brian Spiller commented
In addition the VBE is included with the Office Applications. That makes VBA the default development environment for all users NOT Visual Studio. NOT C+ or C++
BY migrating (or allowing any movement) from VBA then Microsoft will be creating several issue:
Discontinuity from already developed macros and VBA-applications.
Discarding customers (and their work).
Discarding a Building(VBA) that's foundation has been established and is in truth deep.
Microsoft has failed (in the preceding decades) to promote VB in schools where C+, C++ and others have been. That diminished the acceptance by programmers to VB having already studied and learned another competing language.
The industry has failed by moving to XML data, though having certain advantages, is unnecessarily complicated when it comes to raw data (data does NOT need formatting) leaving simple txt files still better for many applications.
When an application creates an XML file of 48MB that is less than 4MB of actual data you realize something is wrong with the XML model!
Bring back and update VB6 programming.
A Green commented
Yes, we need a future for VB6. Include VB6 with Office.
Florence Waters commented
Please do this. Add the VB6 programming language to Office. But it must have the ability to compile to standalone exes.