Project 2010 brought the Ribbon UI, representing the biggest paradigm shift since the introduction of VBA. While the VBA language itself didn't change drastically, the user interaction did. The CommandBars object—once the staple for creating custom menus—was effectively deprecated. Developers now had to customize the Ribbon using XML, a process that was notoriously difficult to do purely within VBA. However, the core object model for tasks and resources remained backward compatible, ensuring that a well-written macro from 1998 could still run in 2010. Core Concepts: Writing Robust VBA Code When programming for the 98–2010 spectrum, "robustness" is the keyword. Code that relies on user interface selection is fragile. The mark of a professional VBA developer is the ability to write code that interacts with data objects, not the screen. 1. The Application and Project Objects Every journey begins with Application . This is the top-level object representing Microsoft Project itself.
In the world of enterprise project management, Microsoft Project has stood as the titan of scheduling and resource management for decades. While the user interface has evolved from the clunky toolbars of the late 90s to the Fluent UI of the modern era, the engine under the hood has remained remarkably consistent. For power users and developers, this consistency is anchored in Visual Basic for Applications (VBA). Project 2010 brought the Ribbon UI, representing the
These versions refined the object model. The introduction of enterprise features (Project Server) began to muddy the waters slightly for VBA, but for the desktop user, the Task and Resource objects became more robust. This era solidified the use of the Application object for global settings and the Projects collection for handling multiple open files. Developers now had to customize the Ribbon using
' This edits the data directly Dim t As Task For Each t In ActiveProject.Tasks If Not t Is Nothing Then t.Name = "Revised: " & t.Name End If Next t This "data-centric" approach works flawlessly across all versions from 98 through 2010 because it bypasses the UI layer entirely. Resource management is often the trickiest part of Project VBA. In Project 98, shared resource pools were prone to corruption if not handled carefully. By 2010, the architecture was more stable, but the coding logic remained consistent. You must check if a resource is `Nothing Code that relies on user interface selection is fragile
Dim pjApp As MSProject.Application Set pjApp = GetObject(, "MSProject.Application") However, for code running inside the Project file, you typically work directly with ActiveProject . This object represents the currently open schedule. The Task object is where the magic happens. In Project 98, iterating through tasks could be slow if done inefficiently. By Project 2010, processors were faster, but best practices remained the same: avoid Select statements.