Microsoft Access Pors and Cons

Neogame

Still learning....
Local time
Today, 09:27
Joined
Jul 4, 2002
Messages
9
Microsoft Access Pros and Cons

Hi I am doing a presentation for University and was wondering if anyone could help me, I need to know a little more about the Pros and Cons of Mircosoft Access (any version).

Thanks
 
Last edited:
I use Access 97 and thought of these... This is stuff I've come across so it's mainly subjective not factual based.

Not that I'm lying to you....

Pros:
  • Ease of use.
  • Usefull tools/reports can be built in short spaces of time.
  • Great depth - Can be simple or extremely complicated.
  • Has a good combination of 4GL and 3GL
  • Powerful
  • Employs SQL (or a variant but it's pretty much the same)
  • Portability - everyone has Access...
  • Easy entry level in programing/application design with a not so steep learning curve.
  • Has built in security functions (though a little tricky to use)
  • Can comunicate with other Microsoft applications fairly easily.
  • Good help system.

Cons:
  • Is a little susceptible to quirky/Illogical operation... I.e. Why the hell is it doing that?
  • Can induce severe headaches after banging your head on the keyboard trying to work out why something isn't happening. Or should I say bad debugger? At least it's easier then debugging a Java app from the comand line compiler...
  • VBA is an Interpreted language so can run slow.
  • Managing and linking many forms can get painful.

Hope this helps...
 
Thanks for your help Emohawk. If anyone else can add to the lists please do, the more the better

thanks
 
Pros

Fantastic program

Cons

You do something one day and completely forget how you did it a week later!

Not much help really...sorry
 
It might help us if you tell us more about the purpose of the presentation. Are you trying to convince them to teach Access or use it for internal development?
 
The purpose of the presentation is to present a discussion on the pros and cons on developing a database program, Basically a company I worked for, want to see the benefits of developing a MRP system in Access (to start off with) but they already have an exisiting program which isnt very good. My presentation needs to argue the pros and cons of both programs and generate a conclusion with recommendation on the way forward. So any help from the people that uses the program is greatly welcome.

thanks.
 
Let me add a few things about Access that might spice it up.

Access pros:

1. It is a Rapid Application Development environment. (RAD is a nice industry buzzword that turns on some programming managers) Using the Access "Wizards" it is possible to build something very fast, then go back and tweak it. In terms of the time it takes to get up and running, this is FAR superior to starting from scratch. Wizards exist for tables, queries, forms, and reports. (OK, Macros and Modules, you're on your own mostly.) But even for class modules, you get some help with event code because things like command buttons have wizards that build the code skeletons for you.

2. It has a fully integrated help system that (at least very often) is context sensitive. And the Help Files can be expanded if you buy the appropriate developer's kit.

3. Access fully integrates with other Office products through the Component Object Model methodology. This means that if you really wanted to get fancy, you could directly import data from Word documents or Excel spreadsheets. Or you could directly export to same. Using only well-defined (ok... REASONABLY well defined) interfaces. There is also a way to work with Web pages (AC2K and ASPs) and an interface for Power-Point.

4. Access is partially object-oriented. We don't get to define base objects that are equivalent in class to tables, queries, etc., but we get to use object-oriented methods on existing base objects. This means, among other things, that it is possible to write generic functions and subroutines that get called and only then find out who called them and from what context.

5. Access supports industry standard concepts very well. I.e. normalization, compound keys, foreign keys, relational integrity, multiple indexes, and many other good features. One-to-one and many-to-one relationships, JOINS, UNIONs, links to external tables or other data sources, importation of text whether through formatted or unformatted files. Lots of good big-system features.

6. If you have the appropriate ODBC drivers, Access can talk to most of the major big-system database.

7. If you have the appropriate networking infrastructure, Access can work over a network.

8. Good support sites are available on the web. Such as this one. And you can get product information from the MS Knowledge Base online, too!

Now, the CONS

1. Access is built with inherent system sizing limits. There are limits to the number of records, number of tables, number of defined system objects, etc. If you have too many forms, reports, tables, queries, macros, and modules, you are sunk.

2. Not only are there limits to the number of things, but sizing is also an issue. Access is built with table, recordset, and database sizing limits that are partially but not completely avoidable.

3. When operating over a network, if the database is in a file that is shared but the application runs on everyone's individual desktop (i.e. multiple copies of Access), network load can become an issue as the number of users increase. (This problem doesn't apply to cases where you have an external database served by an ODBC interface.) The issue is, which machine executes a query? In the simpler case, Access on the desktop does that, so you have massive data transfers to consider. With ODBC, the remote machine does the query and only passes back answers, so the load is mitigated a lot. But the implication is that you had to buy a separate server and product plus the ODBC connectivity pieces-parts to get it to work better.

4. Access security is somewhat limited. Specifically, its "primitives" are VERY primitive. It takes a lot of coding to do anything really fancy with security.

5. Access does not have an inherent journaling feature. You can try to "roll your own" but the tools you will use are relatively primitive for this purpose.

6. Unless you buy a more expensive kit that includes an Access run-time-only system, all users have to have separately licensed copies of Access. This becomes a problem for cranky systems because you will eventually need to hire a desktop maintenance specialist if you have too many users.

7. Graphing under Access is often a pain because you need to know the trick. (There is in fact a knowledge-base article on how to make graphs work right.) This and a thousand other little things can mount up to a very frustrating program that is highly capable but equally quirky. On the other hand, you could say that it assures job security - for psychiatrists... 'cause it's sure to drive you crazy!

8. (Now THIS is personal and you might not wish to include it.) It's a Gates product.
:(
 
Last edited:
I was considering adding that to my list as well but I bought an X-Box the other day and thought it would be hipocritical of me...

Oh well I guess I sold my soul to the devil a long time ago. :rolleyes:
 
I prefer my PS2, Any more additions to the list is welcome, thanks to the others who have already helped.

cheers.
 
I agree with The_Doc_Man's comments, but feel compelled to add the following:

If and when your database 'outgrows' the limitations of Access, you can 'port' your 'back-end' data to MS SQL Server. Once this is accomplished you can minimize the impact of The_Doc_Mans' Cons, numbers 1 through 4. Access still serves handily as a user-friendly 'front-end'

This conversion is not too bad, once you invest in the SQL Server license, and a bit of learning curve.


IMHO, the inherent limitations have been left in Access pretty much unchanged through recent versions and upgrades to Access for marketing purposes, as Mr. Gates and his shareholders need to ensure that you have to buy his more expensive product eventually as your application gains great complexity and/or size. Please do not read too much into this last statement, as I believe Access is a wonderful product for application development and business use, within its defined limitations.
 
I like ACCESS very much. The VBA allows passing parameters from form to queries and also controls the flow of processing.
ACCESS provides a big list of built-in-functions. Help keys are helpful with good examples.

Additionally, no help from DBA is needed. No need to buy him/her coffee everyday for favors.
 

Users who are viewing this thread

Back
Top Bottom