Microsoft Access 2003 [OLD VERSION]

by Microsoft

Product Features

• Supports a variety of data formats, including Extensible Markup Language ( XML ), OLE, Open Database Connectivity ( ODBC ), and Microsoft Windows SharePoint Services
• Access data from multiple databases in forms, reports, and data access pages, linking tables from other Access databases, Microsoft Excel spreadsheets, ODBC data sources, Microsoft SQL Server databases & other sources
• Stored Procedure Designer creates & modifies procedures stored in SQL Server, without requiring you to learn Transact-SQL
• Quickly find tables, queries, forms or reports that depend on a particular database object
• Update properties automatically

Product Details

• Shipping Weight: 7.8 ounces
• Shipping: Currently, item can be shipped only within the U.S. and to APO/FPO addresses. For APO/FPO shipments, please check with the manufacturer regarding warranty and support issues.
• ASIN: B0000AZJV4
• Item model number: 077-02870
• Date first available at Amazon.com: September 12, 2003
• Average Customer Review: 3.4 out of 5 stars  See all reviews (15 customer reviews)
• Amazon Best Sellers Rank: #2,204 in Software (See Top 100 in Software)
  • #16 in Software > Business & Office > Database
• Discontinued by manufacturer: Yes

Product Description

From the Manufacturer

Access 2003 gives you a powerful set of tools that are sophisticated enough for professional developers, yet easy for new users to learn. Create powerful database solutions that make organizing, accessing, and sharing information easier than ever.

Features:

• Use compatible file formats: Access 2000 is the default file format for new databases, so Access 2003 can maintain compatability with existing Access users and solutions.
• Share information more efficiently: export and import data, and link to Windows SharePoint Services sites (requires Microsoft Windows Server 2003 running Windows SharePoint Services).
• Let Access 2003 check for errors: the new error checking feature flags common errors in forms and reports, so you can test and fix errors faster and more easily.
• Incorporate a wide range of data sources: Access 2003 supports data formats such as Extensible Markup Language (XML), OLE, Open Database Connectivity (ODBC), and Windows SharePoint Services.

Product Description

Access 2003 provides a powerful set of tools - sophisticated enough for professional developers, yet easy to learn for new users. Now everyone on your team can create and use powerful database solutions that make organizing and sharing information a breeze. Drag controls onto your Access form to create a Microsoft PivotTable or PivotChart view, or a spreadsheet Powerful Web page database interactivity tools

Customer Reviews

Most Helpful Customer Reviews

76 of 81 people found the following review helpful:

2.0 out of 5 stars Caveat Emptor, June 16, 2005

By 

C. Price "ctp241" (South Africa) - See all my reviews
(REAL NAME)   

This review is from: Microsoft Access 2003 [OLD VERSION] (CD-ROM)

If you're thinking of buying MS Access 2003 there are a few things you need to consider:

1) Microsoft's new licensing/activation requirement for Office products. Office is a serious cash cow and Microsoft are tired of letting people copy it and use it illegally/for free. Access 2003 has a few new features that Access 2000 and 2002 didn't offer, but for most of us they are not worth it - unless web services, xml, smart tags and wizards turn your crank. If you're anything but a developer, most of Access 2003's new features will not be relevant to you.

2) Access is in some respects a powerful database and client-server front-end program and it may be too much for your needs. Using Access can be as simple or complicated as you let it - and it can get very complicated. If you are a small-business owner trying to get organized, you should probably consider another tool like Filemaker. If, on the other hand, you really want to get a handle on things and are prepared to invest some significant time to learn Access and your business and your database needs are growing, then Access might be for you. It is not an easy tool to use, but it is pretty powerful and a lot more usable than middle-market desktop database development tools like FoxPro and Paradox.

3) If you are a small/mid business user and have heard that Access is a great front-end for the free MySQL server-based database engine, also caveat emptor. Access uses ODBC (Open Database Connectivity) to work with MySQL and the implementation is not great so you'll quickly run into some (though solvable) strange problems... and though you could never argue with the price, MySQL itself is a bit on the not-user-friendly side - and finding support when you have a problem is tough.

4) If you are a SQLServer user, or plan to be at some point and intend to use Access as a starter database that you'll eventually migrate to SQLServer (2000 or 2005) or SQLServer Express (2005), then caveat emptor. Microsoft is punting SQLServer Express as their new low-end database - a free version of the bigger SQLServer to compete with MySQL and replace the somewhat clunkily-named and clunkily-implemented MSDE (Microsoft Desktop Database Engine). The new versions of SQLServer are fully committed to Microsoft's .Net platform - essentially a new common platform for new Microsoft products and development tools - which Access/Office is not a part of. Traditionally, many have used Access as a front-end for SQLServer or MSDE databases. Access has provided a great front-end capability for the more grown-up and complicated back-end database servers. The only doubt on the horizon is whether Microsoft are committed to supporting Access properly with future versions of SQLServer. Access Data Projects (an access database front-end for SQLServer 2000) appear to be on the chopping block. You may still be able to use Access files with "linked tables" to access newer SQLServer versions but they can be more difficult to develop and are less than optimal for anything but small database applications. And if you do fit in this category, why would you consider developing a database application at considerable expense when it might not be completely supported by Microsoft in future?

My very personal feeling is that Access is not long for this world. Access as a database application is caught between trying to be a serious database development tool with support for upstream Microsoft products and being a usable database application for small businesses. It appears that increasingly it is not effectively addressing either role. It started life as a serious database tool and then was opted into the Office product lineup where it has pretty much floundered ever since, while SQLServer has been the focus of Microsoft's attention. Sadly, Microsoft seem to have missed the opportunity to develop Access as the stand-alone database and front-end to SQLServer that it could have been.

Ironically, I have been using Access since the first version came out about 10 years ago and, having taken the time to learn it, find it to be an incredible tool for databse front-end development. But it appears that this product is nearing the end of its useful life mostly because Microsoft seem content to not invest much in the product. I certainly hope that Microsoft are just keeping their plans for an Access .Net version that will again integrate with SQLServer quiet, but indications are that there are no such plans.

43 of 47 people found the following review helpful:

4.0 out of 5 stars Access may or may not be for you..., January 7, 2005

By 

DPK (Philadelphia, PA USA) - See all my reviews

This review is from: Microsoft Access 2003 [OLD VERSION] (CD-ROM)

To answer the one reviewer's question, yes -- you need to activate this product (and all products in the Office 2003 suite). Does that suck? Yes. Is it real life and will all the companies who haven't done it in the past start to do it? Damn straight. So that issue, although being one at this point will be all but commonplace a few years from now except for smaller vendors (shareware, etc.) but sooner or later they'll all do it because it's the only way to stop people from copying, copying, copying -- I personally think they should at least give you 2 licenses at a minimum, because you know that's for individual users and small biz owners, but not in this case.

As far as usability and feature-comparison to Access 2000, for a novice user or someone who doesn't "code" (program using computer code) in Access -- I don't recommend the upgrade -- you won't find much of an advantage. There are some nice templates and samples, but they never seem to get you where you want to go for an actual project -- so I recommend sticking w/ 2000 in that case. If you're a programmer and you deploy web sites with Access on Win2K Svr and/or Svr2003 then there are some nice add'l features that make it worth purchasing (which you'll probably get as an upgrade because you already have 2000 and/or complete Office Pro) and it's more stable and reliable than ever before (which isn't saying a lot going back to the older versions), but you've got to upgrade if you fit that category. Quite honestly, if you're building a front-end app in Access then you're going "old school" because it's much more efficient to use a web-based app with Access as the back-end (or SQL, Oracle, etc. for higher-end solutions) -- MySQL is another good option and also runs on different platforms, but you think Access' interface is lousy, don't even bother w/ MySQL then.

If you're a novice looking for a simple database, try some web-based solutions -- chances are the database you're looking for may be out there already. There's completely customizable QuickBase (Intuit product -- makers of Quicken, QBooks, etc.), contact management such as SalesForce.com, among others -- again, not low-end solutions but still options for small biz.

To summarize, if you're a developer or experience with programming in Access, get 2003 (chances are, you already have it) -- if you're a novice or not familiar w/ Access and have 2000 -- not much of a need to upgrade. If you want a version and have a choice between 2003 and 2000, 2003 does have a more polished interface, better wizards, etc. -- it's not easy and intuitive, but still an improvement over 2000 (they have a ways to go). If you're in no rush, just wait until you buy your next PC (probably through Dell, like most of us), and get the Office Pro or Small Biz version with the machine and you'll save hundreds over buying it new -- and don't buy it individually or they really get you with a high cost.

Hope that helps.

22 of 22 people found the following review helpful:

3.0 out of 5 stars Review from an Office developer, August 26, 2005

By 

D. Maruca "_david" (Jacksonville, FL USA) - See all my reviews
(REAL NAME)   

This review is from: Microsoft Access 2003 [OLD VERSION] (CD-ROM)

I've had the pleasure of developing and maintaining a new database in Access 2003 over the past 6 months. The previous 3 years before that I had developed in Access 97 and migrated to Access XP. So, what are my impressions of 2003?

Overall, 2003 is the same great product that XP was with minimal additional features and some new annoying ones. Here is everything from the help file under the "what's new" section for your viewing pleasure:

* View information on object dependencies
* Error checking in forms and reports
* Propagating field properties
* Smart tags
* Back up a database or project
* Windows XP theme support
* Improved sorting in controls
* Autocorrect options
* Enhanced font capabilities in SQL views
* Context-based Help in SQL view
* Importing, exporting, and linking
* XML support
* Security enhancements
More new features...
* New look for Office
* Tablet PC support
* Microsoft Office Online
* Improving quality for the customer (This is a system tray icon that flashes a tool tip asking for feedback much like beta test software)

From this list, the only notable development improvement is the improved XML support, but unless this support is critical to your application development, I would stay far away from this version and stick with XP (which I rate as 5 stars).

I haven't found any improvements to the Visual Basic editor. There are a few new objects you can reference in VBA: dependency collections, smart tag collections, auto-correct, and sub form objects. Form design is mostly unchanged with no new controls to add to forms. They did improve the design interface with smart tags which helps messing around with controls a little. Propagating field properties sounds nice, but has limited use since it only propagates from table design view to all controls that are bound to it. That sounds dangerous. Are you sure you want to push that button not knowing exactly everything it will change?

The feature that I absolutely abhor in 2003 is the security enhancement. Unless you buy a digital certificate from an online authority like Verisign, the end user will be presented with THREE security warnings every time they open the database. This is absolutely ridiculous. There is a small utility that you can run to create a temporary "development" signature, but this only adds to the user confusion as installing this certificate on their machines will only present them with another security warning. Optionally, you can install a jet service pack and set each user's install to run in "sandbox" mode, but then you are limited in the code you can run on their machines which removes the entire purpose of running Access in the first place.