Database Design Optimization - can somebody check it out, please?

[Kyrgyzstanart]

Hello Access Gurus,

I am completely new to MS access and databases overall. Since 2 days I am trying to learn this new tool by watching VTC MS Access 2007 Essentials.

Currently creating a rather simple database w/ the the purpose to:

Track all IT tickets logged by business in my organization.

We would like to be able to enter new IT tickets, track their status, produce concise and detailed reports. Since there are several people in my team logging these IT tickets, we decided to create a DB in which we will store and track them for all team members.

So, I followed the 101 Database Design steps - purpose, data fields, split them into subjects, created relationships and tried a little bit of normalization.

Could you, please, take a look at the tables that I created and let me know if it's an acceptable design or if it could lead to issues going forward? I haven't created any forms, queries or reports yet; as I would like to have some kind of validation on the tables and relationships.

Thank you!

 

[Trevor G]

Hi,

I have had a look at your design of tables and relationships, as long as you want some advice I will hopefully guide you, I am not being critical as building databases aren't as easy as many people think it is.

There are general rules about naming conventions for fields, tables, queries etc. The go along the lines as follows:

Field names should not have spacings (it complicates things later if you need to write VBA code), you can always use the Caption Property to adjust what the users sees.

Be careful about which names you use, as access has reserved words which you can't use.

Naming tables, queries, forms, reports, macros and modules:

follow these

tables begin with tbl
queries begin with qry
forms begin with frm
reports begin with rpt
macros either mcr or mmm
modules mod or bas

No spaces in the names so example tblTeam or qryTeam etc

In your relationship window you are showing tables more than once, not a good practice.

If you are using dates, I wouldn't use the default setting of now() as this records time which will through queries out with problems, use date()