Hardware in the mid-90s was pretty slow compared to computers nowadays, so VBA had to rely on an internal performance cache in order to deliver an acceptable user experience. Although new VBA properties and methods are constantly being added to support innovations in Office, the Visual Basic Editor (VBE) and VBA's inner workings haven't changed much over the last 2 decades in order to ensure consistency and compatibility in the programming model across releases. Visual Basic for Applications (VBA) is a programming language built into most Microsoft Office applications. Eventually, it can make your add-ins unstable: weird errors crop up, stuff that makes no sense and that you can't fix in code because it's not the code that causes the problem.
As you edit your source code over time, the size of the file grows in ways that make no sense and the bloat makes its way into the add-ins you compile.
Does your VBA program behave erratically or stops with an incomprehensible error?
0 kommentar(er)
