Microsoft Access is a relational database management system (DBMS). At the most basic level, a DBMS

University Degree Mathematical and Computer Sciences

Introduction: What is Access?

Microsoft Access is a relational database management system (DBMS). At the most basic level, a DBMS is a program that facilitates the storage and retrieval of structured information on a computer’s hard drive. Examples of well-know industrial-strength relational DBMSes include

• Oracle

• Microsoft SQL Server

• IBM DB2

• Informix

Well-know PC-based (“desktop”) relational DBMSes include

• Microsoft Access

• Microsoft FoxPro

• Borland dBase

The advantages of developing applications in Access are as follows:

1. Access is easily installed on a PC

2. Access is relatively easy to pick up

3. Access does not require a server unless you attempt to share it

4. An individual can learn the basics of databases from it

1. Give description of the organization it most represents.

Access is widely used by small businesses and hobby programmers to create ad hoc customized systems for handling small tasks. Its ease of use and powerful design tools give the non-professional programmer a lot of power for little effort. However, this ease of use can be misleading. This sort of developer is often an office worker with little or no training in application or data design. Because Access makes it possible even for such developers to create usable systems, many are misled into thinking that the tool itself is limited to such applications.

2. The tasks/process, it is specifically designed for.

Professional application developers use Access for , especially for the creation of prototypes and standalone applications that serve as tools for on-the-road salesmen. Access does not 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 , , , , , or . However, an Access "front end" (the forms, reports, queries and code) can be used against a host of database backends, including Access itself, SQL Server, Oracle, ...

This is a preview of the whole essay

2. The tasks/process, it is specifically designed for.

Following are the reasons to use Microsoft Access:

1. Support - Microsoft Access is one of the best-selling desktop databases of all time. You can be sure of future support and with Microsoft's backing, should be around for some time.

2. Scalable - Access has an upgrade path. So, if performance starts to suffer from an ever increasing number of users or records, you can upsize to SQL Server.

3. RAD - One can use Access for Rapid Application Development thus keeping costs down. Its object oriented model means you can build attractive, functional and easy to use applications in double-quick time.

4. Integration - Access has works well with the Microsoft Office suite. It has been designed with integration in mind. If MS Office is your preferred suite then it makes sense to seriously consider Access as your database of choice.

5. Legacy data - Access can import many data formats so your existing data is not lost.

6. Web integration - Access (2000 particularly) has close web links so online data access is made easier. With a shift towards e-commerce, Access's web integration could prove very useful, if not now, then sometime in the near future.

3. Is it an object oriented development, explain. If not then can it be developed on the 4GT (4th generation tool), explain.

One of the benefits of Access from a programmer's perspective is its relative compatibility with – 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 and "Macros" for programming forms and logic and offers object-oriented possibilities. Its object oriented model means you can build attractive, functional and easy to use applications in double-quick time.

4. Do you think it requires extensive tests, why?

The Access package contains the following elements:

• A relational database system that supports two industry standard query languages: Structured Query Language (SQL) and Query By Example (QBE);

• A full-featured procedural programming language—essentially a subset of Visual Basic,

• A simplified procedural macro language unique to Access;

• A rapid application development environment complete with visual form and report development tools;

• A sprinkling of objected-oriented extensions; and,

• Various wizards and builders to make development easier.

For new users, these “multiple personalities” can be a source of enormous frustration. The problem is that each personality is based on a different set of assumptions and a different view of computing. For instance,

• The relational database personality expects you to view your application as sets of data;

• The procedural programming personality expects you to view your application as commands to be executed sequentially;

• The object-oriented personality expects you to view your application as objects which encapsulate state and behavior information.

Microsoft makes no effort to provide an overall logical integration of these personalities (indeed, it is unlikely that such an integration is possible). Instead, it is up to you as a developer to pick and choose the best approach to implementing your application. Since there are often several vastly different ways to implement a particular feature in Access, recognizing the different personalities and exploiting the best features (and avoiding the pitfalls) of each are important skills for Access developers.

The advantage of these multiple personalities is that it is possible to use Access to learn about an enormous range of information systems concepts without having to interact with a large number of “single-personality” tools, for example:

• Oracle for relational databases

• PowerBuilder for rapid applications development,

• Smalltalk for object-oriented programming.

So because of the aforesaid reasons no extensive tests are required.