Designing and Deploying Office Solutions
This content is no longer actively maintained. It is provided as is, for anyone who may still be using these technologies, with no warranties or claims of accuracy with regard to the most recent product version or service release.
Chances are good that you're reading this book because you need to develop a Microsoft Office-based solution for your company. If your company is like most companies, it needs to be done yesterday, and you're already wondering how you're going to get it done on time. However, we're also willing to wager that despite the stress of building a bullet-proof application in record time, you also secretly (or maybe not so secretly) think that writing code in Visual Basic for Applications (VBA) is a lot of fun. And we agree. For many people, coding is more fun than designing and planning a solution, and it's tempting to jump right in and begin coding before you've fully thought through the problems that you're facing. The goal of this chapter is to persuade you to go through that sometimes difficult design process in order to begin coding with a clear goal in mind. Spending a few hours up front on design can mean the difference between delivering the solution that your customer needs a few months down the road, or backtracking to try to convert your many hours of coding work into the solution that you wish you had designed in the first place.
Contents
Which Technologies Should You Use?
Thinking About User Interface Design
Designing Code for Reusability