7 Horrible Mistakes You’re Making With Database Application

Application Error


In the wonderful world of database applications creation, there are many types of users. Let’s just say that some are better than others… To illustrate the biggest mistakes users make when creating database applications, here are the 7 types of users you don’t want in your team.


The Field Misuser

Your online database software is offering a wide array of fields to build your application with. Each field has its own set of properties and it should be used accordingly to ensure the best possible compilation of the data. The Field Misuser simply don’t understand the different types of fields. He is using single line text for dates and dropdowns for user lists. Not using the fields to the best of their properties will give you a migraine when the times come to create your searches and reports. Of course, dates put in a single line text won’t show up in a calendar view. Same for your users put in a dropdown, notification won’t be able to occur.


The Micromanager

Mandatory fields are great to make sure the users don’t forget to type in vital informations. Your database application will always contain a minimum of one single line text mandatory field to be able to name your item. But then, making too many fields mandatory put some strain on the user. Each and every time you try to save a new item without filling in the mandatory fields, the system will give you a reminding message to enter the missing information. Stop micromanaging and trust your user to fill in all the important fields. If they don’t, maybe you’re also The Freudian? Keep reading!


The Illogical

The Illogical is all over the place. Even if he understands the properties of each field and is using them properly, he simply doesn’t understand the order in which the fields should be placed. There is absolutely no flow. There are mandatory fields at the end of the application, the creation date is on top and the name of the item is in the middle. This type of application will cost you a lot of time trying to figure out what information is required, if it’s not is simply impossible to use.


The Visually Unpleasant

The Visually Unpleasant understands the properties of each field and there is good flow in his application. The only thing is, his applications are ugly. Fields aren’t visually grouped and all his rows and columns are of different width and height. Some labels are narrow and some are wide. Some users won’t mind a visually unpleasant application but if you are like me, you it will burn your eyes and make you cry. Clean up!


The Napoleon

Let’s put this one simply: bigger is not always better. The Napoleon likes to upload huge files, he is creating way too many unnecessary fields and is using tons of description fields to give orders to his troops. The Napoleon don’t like to create sections. Don’t create your applications giving the impression to other users that you have something to prove. If you do, you’l be called The Napoleon and nobody wants that nickname, right?


The Destroyer

The Destroyer is sneaky, you will not necessarily see him coming. But beware, he will, well, destroy (!) your application. The Destroyer gives the impression that he understands the basic data architecture. He will tell you that he understands that the application is the blueprint for the projects and that items belong in projects. Great! He seems so knowledgeable that you gave him the “application administrator” permission. He can now create, edit and delete your account’s applications. On a busy Monday morning, he will email you a screenshot where you can see that he deleted the application instead of deleting a search. Stop everything, read this article and give him “view only” permissions for a couple of days.


The Corrupter

The Corrupter’s intentions are shady. You will never be sure you understand what his deal is. Behind everybody’s back, he goes and change the data in some items. Maybe he simply forgot something and just wanted to make sure the data is complete, or maybe his intentions aren’t that good. Who knows? If you have a Corrupter in your team, remember yourself (and him!) that you can always have access to the history for each and every item. You have access to by whom and when the data was amended. If you simply need to stop the Corrupter, make sure your sensitive fields have the property “write once”. This will do the trick to prevent him to edit already saved data.


Do you recognize any of these big mistakes being made by those disturbing users in your account? I’m sure we can add to the list, please leave a comment with your story.



This entry was posted in Database Application. Bookmark the permalink.