INFRASTRUCTURE OF A DATABASE

Data is added, removed, updated, and queried using Access as the interface design tool. Access may
also be used to see the database through the forms that have been created. In general, we may use
forms to manage data access, such as which data fields are displayed. Certain users, for example, may
not require access to all the fields in a table. It's easier for us to use the database if we give those users
a form with only the fields they need. Because consumers don't have to seek for what they need, an
effective form speeds up database utilisation. Working with the database is more enjoyable and
efficient when the form is aesthetically appealing, and it may also assist prevent inaccurate data from
being input. While data may be simply put into a table, the larger the table becomes, the more difficult
it is to ensure that the data is in the correct field and record.

CREATE TABLE
A table is a well-organized structure for storing data. It contains of fields of data into which you enter
the table's records. A field is a single column in a database that contains just one type of data. A
record is a group of linked fields that describe a single object and are stored in a table row. The tables
below were created in Access and contain the data sheet of the menu like meals and drinks.

The actual data contained in the table will not be visible in the "Design View." The table structure is
the only thing represented in the window. The data contained in the form can be viewed through the
“Layout View.” Using "Datasheet View" to build tables will allow you more control over field
properties. There are two panes in this window. The top of the page has a “design grid” where we can
enter field names and data types. After that, there is the "properties" section.

Properties field
 Design View

Datasheet View

CREATING FORM
To create form, we need to go to create then click the “Form” logo. After that you can insert the data
in the form. The form that has been created as follow:

As shown in the Restaurant Form the diagram above, shows the number of orders of each type of food
and beverage that have been ordered by the customer. At the bottom of the form there is the total price
of all orders that have been ordered by the customer. The total price is formulated which is the price
times the quantity to get the result.
CONCLUSION
In conclusion, the database created can make it easier for the market to track business objectives.
Database design is basically a time-consuming process. The more you can predict and accommodate
this in a database architecture, the more efficient and less annoying the database will be in the future.
There is no perfect database, and the only way to know if a database is good is if it performs the
functions you expect. Your design is effective if you can handle the information from your sources the
way you need it, perform the analysis you need and be as flexible as you need in each of these areas.
The new thing to learn is when the information you want to analyse often shows up, but you don’t
know where to put it. Monitor your data types and make changes as needed. Find data that can be
categorized or standardized. Lastly, keep an eye on data that you didn’t expect when creating a
database.