Microsoft Access
From Wikipedia, the free encyclopedia
Jump to: navigation, search
Microsoft Access
Microsoft Office Access 2003 Screenshot
Developer: Microsoft
Latest release: 2003 for Windows / October 2003 (Windows)
OS: Microsoft Windows
Use: RDBMS
Website: office.microsoft.com/access
Microsoft Access (current full name Microsoft Office Access) is a relational database management system from Microsoft, packaged with Microsoft Office Professional which combines the relational Microsoft Jet Database Engine with a graphical user interface.
Microsoft Access can use data stored in Access/Jet, Microsoft SQL Server, Oracle, or any ODBC-compliant data container. Skilled software developers and data architects use it to develop application software. Relatively unskilled programmers and non-programmer "power users" can use it to build simple applications. It supports some object-oriented (OO) techniques but falls short of being a fully OO development tool.
Microsoft Access was also the name of a communications program from Microsoft, meant to compete with ProComm and other programs. This Microsoft Access proved a failure and was dropped. Years later Microsoft reused the name for its database software.
History
Microsoft Access version 1.0 was released in November 1992.
Microsoft specified the minimum operating system for Version 1.1 as Microsoft Windows v3.0 with 4 MB of RAM. 6 MB RAM was recommended along with a minimum of 8 MB of available hard disk space (14 MB hard disk space recommended). The product was shipped on seven 1.44 MB diskettes. The manual shows a 1993 copyright date.
The software worked well with very large records sets but testing showed some circumstances caused data corruption. For example, file sizes over 700 MB were problematic. (Note that most hard disks were smaller than 700 MB at the time this was in wide use). The Getting Started manual warns about a number of circumstances where obsolete device drivers or incorrect configurations can cause data loss.
MS-Access's initial codename was Cirrus. This was developed before Visual Basic and the forms engine was called Ruby. Bill Gates saw the prototypes and decided that the Basic language component should be co-developed as a separate expandable application. This project was called Thunder. The two projects were developed separately as the underlying forms engines were incompatible with each other; however, these were merged together again after VBA.
Uses
Access is used by small businesses, within departments of large corporations, and hobby programmers to create ad hoc customized desktop systems for handling the creation and manipulation of data. Access is not designed to build full web or browser based systems - tools like PHP/MySQL or Microsoft SQL Server or ASP or Alpha Five are better suited for this.
Some professional application developers use Access for rapid application development, especially for the creation of prototypes and standalone applications that serve as tools for on-the-road salesmen. Access does not scale well if data access is via a network, so applications that are used by more than a handful of people tend to rely on a Client-Server based solution such as Oracle, DB2, Microsoft SQL Server, Windows SharePoint Services, PostgreSQL, MySQL, Alpha Five, MaxDB, or FileMaker. However, an Access "front end" (the forms, reports, queries and VB code) can be used against a host of database backends, including Access itself, Microsoft SQL Server, Oracle, and any other ODBC-compliant product.
Many developers who use Microsoft Access use the Leszynski naming convention, though this is not universal; it is a programming convention, not a DBMS-enforced rule.
Features
One of the benefits of Access from a programmer's perspective is its relative compatibility with SQL – queries may be viewed and edited as SQL statements, and SQL statements can be used directly in Macros and VBA Modules to manipulate Access tables. Users may mix and use both VBA and "Macros" for programming forms and logic and offers object-oriented possibilities.
MSDE (Microsoft SQL Server Desktop Engine) 2000, a mini-version of MS SQL Server 2000, is included with the developer edition of Office XP and may be used with Access as an alternative to the Jet Database Engine.
Unlike a complete RDBMS, the Jet Engine lacks database triggers and stored procedures. Starting in MS Access 2000 (Jet 4.0), there is a syntax that allows creating queries with parameters, in a way that looks like creating stored procedures, but these procedures are limited to one statement per procedure.[1] Microsoft Access does allow forms to contain code that is triggered as changes are made to the underlying table (as long as the modifications are done only with that form), and it is common to use pass-through queries and other techniques in Access to run stored procedures in RDBMSs that support these.
In ADP files (supported in MS Access 2000 and later), the database-related features are entirely different, because this type of file connects to a MSDE or Microsoft SQL Server, instead of using the Jet Engine. Thus, it supports the creation of nearly all objects in the underlying server (tables with constraints and triggers, views, stored procedures and UDF-s). However, only forms, reports, macros and modules are stored in the ADP file (the other objects are stored in the back-end database).
Development
The programming language available in Access is, as in other products of the Microsoft Office suite, Microsoft Visual Basic for Applications. Two database access libraries of COM components are provided: the legacy Data Access Objects (DAO), only available with Access, and the new ActiveX Data Objects (ADO).
Microsoft Access can be applied to small projects but scales poorly to large projects owing to weak security, file size and database locking features.
All database queries, forms, and reports are stored in the database, and in keeping with the ideals of the relational model, there is no possibility of making a physically structured hierarchy with them.
One design technique is to divide an Access application between data and programs. One database should contain only tables and relationships, while another would have all programs, forms, reports and queries, and links to the first database tables. Unfortunately, Access allows no relative paths when linking, so the development environment should have the same path as the production environment (though it is possible to write a "dynamic-linker" routine in VBA that can search out a certain back-end file by searching through the directory tree, if it can't find it in the current path). This technique also allows the developer to divide the application among different files, so some structure is possible.
One limitation of the programming environment is that controls must have "the focus" for their properties or methods to be accessed. Thus, if gaining or losing focus triggers any event handlers a cascading error will occur. Some programmers have speculated that this is a marketing strategem on the port of Microsoft to spur upgrade to VB or Visual Studio.
References
This article or section does not cite its references or sources.
You can help Wikipedia by introducing appropriate citations.
Further reading
"New life for old Microsoft Access data"
"Microsoft Office Access 2003 Inside Out" by John L. Viescas
"Database Design for Mere Mortals" by Michael J. Hernandez
"Access Database Design & Programming" by Steven Roman
"Access 2002 Developer's Handbook⢠Set By Paul Litwin; Ken Getz; Mike Gunderloy
"Succeeding in Business with Microsoft Office Access 2003: A Problem-Solving Approach" by Karin Bast, Leon Cygman, Gerard Flynn, Rebekah Tidwell
"Access 2003 VBA Programmer's Reference" by Patricia Cardoza, Teresa Hennig, Graham Seach, Armen Stein
"SQL Access to SQL Server" Published by Apress - Susan Sales Harkins and Martin WP Reid
"Mastering Microsoft Office Access 2003" Published by Sams - Alison Balter
Versions
Versions for Microsoft Windows include:
1993 Access 2.0 for Windows (Office 4.3)
1995 Access 7 for Windows 95 (Office '95 Pro)
1997 Access 97 (Office '97 Pro)
1999 Access 2000 (Office 2000 Pro & Premium)
2001 Access 2002 (Office XP Pro)
2003 Access 2003 (Office 2003)
2007 Microsoft Office Access 2007 (2007 Microsoft Office system)
Notice: There is no Access 3.0 to 6.0, because the Windows 95 version was launched with Word 7. All the Office 95 products have OLE 2 capacity - moving data automatically from various programmes - and Access 7 should show that it was contemporary with Word 7.
Also you can go to these websites:
http://office.microsoft.com/en-us/access/FX100487571033.aspx
http://www.toyecorp.com/msaccess.html
Hope these help you out.
2006-11-29 05:05:14
·
answer #4
·
answered by babygirl 3
·
0⤊
0⤋