- Platform: Windows 2000 / XP
- Media: CD-ROM
- Item Quantity: 1
|
||||||||||||||||||||
|
||||||||||||||||||||
|
||||||||||||||||||||
System Requirements
Product Details
|
Product Description
From Amazon.co.uk
Office Access 2003 is a database manager, which makes it suitable for storing structured data such as catalogues, stock records or customer lists. Using Office Access 2003, you can also create data entry forms, queries and reports, or complete applications programmed using VBA (Visual Basic for Applications). All these elements are saved to a single .MDB file, making it easy to copy and distribute Access database projects.
The popularity of Access is based on several strong features. The interface is clean and uncluttered, and you can open data tables in a familiar spreadsheet-like view. There is a visual query builder, or you can write queries in SQL, the standard database query language. Advanced features let you enforce relational integrity between tables and set validation constraints on fields. There is also an excellent report designer. The Access database engine is not suitable for very large databases, but you can scale up by switching to Microsoft's SQL Server or an ODBC database while still using the same visual tools. New in Office Access 2003 is automatic error-checking in forms, integrated support for transforming data with XSL (an XML standard), and the ability to link to lists in SharePoint Services as a convenient way to share data. A small but welcome detail is control over the font used in the SQL editor, which was fixed at a small size in earlier versions.
This is a capable product and generally a pleasure to use. The main gripe against it is that even Microsoft's wizards do not make relational database applications easy to build. FileMaker is better for non-specialists, but Office Access 2003 wins on Office integration and more comprehensive features. --Tim Anderson
Product Description
Share information more efficiently.
Export and import data, and link to lists on Windows SharePoint Services sites where other team members can access them. Building these sites requires Microsoft Windows Server 2003 running Windows SharePoint Services.
Help eliminate errors.
The new error checking feature flags common errors in forms and reports, making testing and fixing errors faster. After errors are flagged, you are given options to correct the errors, saving time and helping you to create more accurate forms and reports.
Export and import data, and link to lists on Windows SharePoint Services sites where other team members can access them. Building these sites requires Microsoft Windows Server 2003 running Windows SharePoint Services.
Help eliminate errors.
The new error checking feature flags common errors in forms and reports, making testing and fixing errors faster. After errors are flagged, you are given options to correct the errors, saving time and helping you to create more accurate forms and reports.
Improved Features
Incorporate a wide range of data sources.
Access 2003 supports a variety of data formats, including Extensible Markup Language (XML), OLE, Open Database Connectivity (ODBC), and Microsoft Windows® SharePoint Services.
Link business systems.
Link tables so that you can access data from multiple databases at one time in Access 2003 forms, reports, and data access pages. Link tables from other Access databases, Microsoft Excel spreadsheets, ODBC data sources, Microsoft SQL Server databases, and other data sources.
Get the most from your enterprise data.
Incorporate Microsoft SQL Server-based data into your Access solutions. Use the Stored Procedure Designer to create and modify simple procedures stored in SQL Server without having to learn Transact-SQL.
Give your forms a new look.
Microsoft Office Access 2003 supports themes from Microsoft Windows XP to give your forms a consistent design.
View dependency information.
Quickly find tables, queries, forms, or reports that depend on a particular database object.
Update properties automatically.
Change a field property in a table and all the forms or reports that have controls bound to it can be updated automatically.
Analyze your information in powerful ways.
Drag controls onto your Access form to create a Microsoft PivotTable or Microsoft PivotChart view, or a spreadsheet.
Easily back up your information
In Access 2003, you can save a copy of the database you're working on to another location.
Design Web pages using powerful tools.
Publish forms and reports on the Web and bind your information to a record source to display, update, and work with data from your database.
Use compatible file formats.
Microsoft Office Access 2003 uses Microsoft Access 2000 as the default file format for new databases. Because Microsoft Access version 2002 and Microsoft Access 2000 can use and modify the same database, organizations can roll out Microsoft Office Access 2003 while maintaining capability with existing Access users and solutions.
Find the help you need.
From the Getting Started and Help task panes, you can access Assistance on Microsoft Office Online. It provides help and assistance articles that are updated regularly from requests and issues of other users. Some functionality in these task panes requires a connection to the Internet.
Tag this product(What's this?)Think of a tag as a keyword or label you consider is strongly related to this product.
Tags will help all customers organize and find favorite items. |
Customer Reviews
Most helpful customer reviews
License agreement includes internet activation?
Oct 23 2003
Hi folks.
I bought MS Access 2000 3 years ago. Then I upgraded to their next version MS Access 2002 upgrade but it had a policy of only working on the first computer you installed it on due to internet activation. I had two PCs(one a test PC that tends to get reimaged a lot) so that didn't work out too well and I switched back to Access 2000 and dumped the 2002 CD as my refund date had passed.
Does this new MS Access 2003 have the same policy? If so I won't buy it. Also does this new version have any "gotta have it" features or is it just the same old application made a little prettier?
I'd need a good reason to buy MS Access 2003. Lately I've been looking at other products like Star Office. Unfortunately their 6.0 version didn't have as easy a database as MS Access and Star Office didn't document that part much. I haven't seen their 7.0 version yet.
I gave this review 3 stars because I'm pretty sure Access 2003 will meet my needs if it's anywhere as good as Access 2000, but I don't like Microsoft's licensing policy and internet activation. If they have that, I won't buy. So please post a review and let me know.
Puts data in motion for any company.
Oct 22 2003
This new version of Access is also XML integrated, enhanced features such as extraction of data from multiple tables, Access 2003 also improves Smart Tag integration. The ability to design solutions within the program makes web services a powerful resource for the enterprise; the flawless integration with Microsoft SQL makes information sharing a productive experience. This makes data storing and retrieval an easy way to control how data is implemented across many scenarios using personalized solutions, allowing your information to have a stronger impact across the Enterprise.
Most Helpful Customer Reviews on Amazon.com (beta)
Amazon.com:
15 reviews
76 of 81 people found the following review helpful
Caveat Emptor
Jun 16 2005
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.
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
Access may or may not be for you...
Jan 7 2005
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.
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
Review from an Office developer
Aug 26 2005
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.
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.
