Accountants Should Dump Microsoft Excel for Microsoft Access Database

Accountants Should Dump Microsoft Excel for Microsoft Access Database

I’ve been saying this for years, Microsoft Access databases is simply far better than Excel. In fact Access is just Excel on steroids!

As the following link to this article says “we are all Excel-aholics who can’t get through the day without busting out a spreadsheet…“. 

Here’s the article link: http://goingconcern.com/post/accountants-should-dump-microsoft-excel-database-software

Accountants Should Dump Microsoft Excel for Microsoft Access Database

Accountants Should Dump Microsoft Excel for Microsoft Access Database

The default reaction is to lean towards Excel and that’s understandable but that’s because it’s how we are all first taught to use this application and the ease of how a spreadsheet  can be to manipulate data and analyse out.

But where data integrity and security protection  is key to the maintenance and workflows of a system, you simple have to consider Microsoft Access databases.

There’s also a compromise where both could be used and this maybe a fair outcome to get the best of both using their strengths and dismissing the weaknesses at the same time.

Want to learn more? Take a look at my eBook bundle covering the key objects of Microsoft Access database.

Microsoft Access Database Normalization Versus DeNormalization

Microsoft Access Database Normalization Versus De-Normalization

To normalize or to de-normalize that is the question!

Database normalization is widely misunderstood. Any new database system should adopt some level of database normalization (a minimum of ‘Third Normal Form (3NF)’) but what does this really mean?

The idea behind database normalization is to protect and maintain the data integrity keeping your data complete and consistent when storing data (input) to handling effective reporting (output). Keeping records in one place which can be related and impact data values in other places is the trick and this is why normalization is normally the methodology used here when designing an Access database.

Having smaller and re-usable manageable units of information maintains Continue reading “Microsoft Access Database Normalization Versus DeNormalization”

How to Utilise and Apply Access Database Normalisation Techniques

Access Database Normalisation levels 1, 2, 3; getting normal about it!

The process of Database Normalisation was developed by E.F.Codd who is widely considered the father of relational database theory.

There are several rules which provide theoretical structures and disciplines which are not always practical to follow but help provide the main goals which are:

  1. Eliminate redundant information
  2. Increase data integrity
  3. Make systems more efficient

Modern databases should be in BCNF Boyce-Codd Normal Form which is deemed to be at third normal form of which there are considered to be five in all. This article focuses on what I believe is considered a good balance to applying some of these rules and covers up to the third norm of database normalisation.

Continue reading “How to Utilise and Apply Access Database Normalisation Techniques”