Great! So applying a basic knowledge of custom fields and Project VBA programming will enable us to create a custom field for displaying the material costs of tasks. Refer to the blog Using Microsoft Project Custom Fields for an introduction to custom fields. In addition to the Project VBA basics creating a material cost field also requires a rudimentary understanding of Microsoft Project custom fields. I was even recommended the following VBA Project programming book “VBA Programming for Microsoft Project ’98 through 2010 with an introduction to VSTO” by Rod Gill. Well, by consulting a Microsoft Project discussion forum I quickly found the required VBA subroutine for listing task material cost.
#VISUAL BASIC FOR APPLICATIONS TUTORIAL PDF HOW TO#
But knowing how to program Project VBAs, apparently, opens the door to a myriad of project data in Microsoft Project. I don’t intend to validate the accuracy of my brother-in-law’s theory. My question is why would project data as simple as listing the material cost require a VBA subroutine extension? My brother-in-law, a computer science professor, surmises that Microsoft, most likely, intentionally left out the material cost field to nudge all us novice Microsoft Project users towards programming Project VBAs.
Apparently, displaying this project data requires the insertion of a Visual Basic Application (VBA) subroutine for Microsoft Project. I was somewhat surprised to discover that the standard Microsoft Project installation does not have a variable or field for displaying the resource material cost of tasks.
0 kommentar(er)
