For each table, there needs to be a unique identifier, or what's called a primary key. The primary key allows us to differentiate each record so we can get the proper content when we find that unique ID.
Let's bring back our user requirements again and see what we need to do.
Looking at the requirements, which would you choose to be the unique identifier or the primary key? Every incident needs a unique number so it can be tracked.
Right away, this requirement should jump out at you saying "USE ME AS A PRIMARY KEY!" By knowing the primary key of the table we're going to create, we can begin to create our table.
Let's do it! On the Object Designer screen, do the following:
For the organization of the table, let's create the fields for our primary keys first. Enter the information as shown in the following example:
It's good practice to increment Field No. by 10 instead of...