What do we mean when we say fields and records? Well, a table is divided into columns and rows, just like a grid in a spreadsheet program.
- each column is considered a field and represents the kind of information you are displaying
- each row is considered a record and is the collected value of that information
Let’s imagine a hypothetical, super-simple Customer table.
The above Customer table is divided into three columns: first name, last name, and email. As mentioned before, in Method terminology, each of the three columns is considered a field.
Likewise, each row in the grid, containing customers Bob, Amy, and Valerie, is considered a record.
See how these two interact? The record refers to a specific customer, and the fields determine what information is associated with that customer. You really only require a single field in order for Method to save a record, but the more fields that are associated with a record, the more specific the record becomes.
It’s important to note that Method automatically assigns a unique number to each record in a table as an identifier. This number is known as the Record ID.
The Record ID is used to uniquely identify a record. So if you have two, three, or more records where all the fields are the same, they will still be distinguished by the unique Record ID.
Even if you delete the record, that unique number will never be used again in that table - the next record created after that will be assigned the next sequential number (say, 46).