by Troy Janisch
If you told other developers that you were considering Microsoft Access to manage content for a large Web site, they'd probably think you were going to do something stupid.
Stupid, that is, until you share the strategies discussed in this article.
There are many good reasons not to recommend Microsoft Access for large Web site development projects. These reasons include things like MySQL, SQL Server, and Oracle. As a result, it's not uncommon to bypass Microsoft Access quicker than the neglected stall of a truck stop restroom. However, if you can plug your nose and bear with me for a few sentences, the natural revulsion that you have for Microsoft Access may dissipate.
When considering Microsoft Access in a client/server context, such as the Web, the key is to focus on the first half of the client/server equation. While Microsoft Access can be a dismal server-side solution, it turns out to be one of the best client programs imaginable. It connects to Oracle, SQL Server, MySQL and other OBDC-compliant data sources. It connects to several different types of data sources simultaneously. It enforces database schema and database user privileges. Basically, it?s a Swiss-Army knife of database clients.
Microsoft Access allows you, or your customers, to update Web site content in real time using a desktop client application. Furthermore, since Microsoft Access has its own password protection, reporting, graphing, and data-entry capabilities -- it provides a more comprehensive way to update and manage Web content than a typical Web-based interface you'd have to create.
Implementing Microsoft Access as a database client can be done quickly -- all you need to do is create a database user account, install the proper OBDC driver(s) and link to remote tables. It can also be done for little cost since owning Microsoft Office on the PC typically means owning Microsoft Access. Even if your customer doesn't own MS Access, buying it is often less expensive than the time it takes to create a Web-based content management tool.
I've also found that more clients find more value from being able to use MS Access to manage their Web site than from having to maintain customWeb-based tools. Recently, despite having a full-featured Web-based content management system, prefers using MS Access to manage 10 e-commerce sites.
By now, perhaps you've unplugged your to the possibilities that Microsoft Access presents. If not, maybe you've probably at least raised an eyebrow. Either way, just remember that liking Microsoft Access more doesn't have to mean hating Microsoft any less.
