Since 1986, at FMS, we've created countless custom databases for a variety of organizations, along with a wide range of developer tools.

One thing I've learned is that database problems haven't changed. Yes, we went from DOS to Windows, Access took over the desktop database market, and the Web offers a new way to use data. But in the end, there's still the fundamental need to store, track, and analyze data. The business reasons for databases haven't changed significantly. People still have to get their job done, and databases support their efforts.

When Access appeared in 1992, and this magazine was born, it took over the desktop database market. People forget that back then, Borland held 85 percent of the market with dBASE and Paradox, while Microsoft held a small piece with just acquired FoxPro. Access is now the most popular database in the world, and Borland is out of the desktop database business. Having front row seats to the transformation was incredible. FMS was closely allied with Borland, and it was my first experience seeing a market bubble burst. Fortunately, we hedged our bets and evolved into a Microsoft Access shop that now supports SQL Server, Visual Basic, Visual Studio .NET, and other related technologies.

The evolution of Access
For me, it's all about evolution. Evolution never ends. Some people fight it, while others prepare for it. Those who fight it eventually go extinct.

Over the years, we've seen Access evolve through many versions. Access 2.0 was a winner but became extinct when its 16-bit ecosystem disappeared. Access 95 deserved to die, while Access 97 was a great product. Access 2000 introduced ADPs and significantly enhanced connections to SQL Server, but broke database compatibility with Access 97. Much to Microsoft's chagrin, this incompatibility continues to cause migration difficulties from Office 97 to Office 2000 and XP. There are simply too many Access 97 applications that no one wants to touch, but may need conversion for the migration.

With Access 2002/XP and now Access 2003, Microsoft added features to extend connectivity and the capabilities of Access developers. But the Access world isn't entirely safe. FileMaker is in our ecosystem and appeals to the less sophisticated. Although Microsoft neglects to add features for user productivity (which also help developers), FileMaker continues to make inroads. It's the small mammal in the age of dinosaurs.

Access remains a powerful database that meets the needs of the largest segment of the database ecosystem -- in particular, multi-user, Windows-based database solutions involving data entry, viewing data, querying data, and reports. Yet, Access is often perceived as a toy or somehow inappropriate for professional application development. I couldn't disagree with this more. Access remains the best tool for a wide range of database challenges in any organization.

Developer and database trends
I believe the misconception of Access' role is a result of two evolutionary trends: the application developer and the nature of databases.

Most Access developers evolved from non-programming professions. They fell into Access, discovered the amazing productivity gains, learned VBA, and become more and more sophisticated. Over time, many became VB and .NET developers using SQL Server, and now consider Access applications trivial. But the change is with the developer and not Access. Access still does what it does well, but these people are ready to move on. They now look down on people like their former selves challenged by database fundamentals they take for granted today. They forget Access was their gateway to a successful career. Their evolution away from Access is OK and even expected, as others follow in their footsteps discovering the amazing solutions they can create with Access.

The second evolutionary trend is with databases. Database applications aren't simply created once. Healthy database applications change and grow over time, bad ones become extinct, and sometimes good ones die when their environment changes. Good IT managers use Access strategically and anticipate only a tiny percentage of Access applications ever need to migrate to more powerful platforms. Sure, it would have been better to build that Access application differently from the beginning or maybe use a more qualified developer, but it's impossible to predict which one of the 100 databases today will need to migrate in three years. Most will run perfectly fine in Access forever or become extinct. Making a bigger investment today makes no sense when a simpler, less risky Access solution is possible. Unfortunately, some people get confused when they see a bunch of Access applications that need to evolve and blame Access. They fail to realize what they're observing isn't because of Access; it's just the natural evolution of the application.

The beauty is that Access is feature-rich and lets developers transform simple Access applications, migrate Jet to SQL Server, or simply move on, using the Access application as a prototype. Anticipate database evolution and let time determine which databases survive to justify additional investments to take them to the next level.

Access' competitive advantage
So, it's all about evolution. Some developers will evolve away from Access, just like some Access applications will evolve from Jet or Access completely. Regardless, Access is still the best solution for a wide range of database needs, and those who capitalize on its strengths bring a competitive advantage to themselves and their organizations.