Suggestion for database

[Myself2019]

Dear everybody,

I need some suggestion as I am planning to create a new database with a form associated.
Here are the field

#ID - numbers
#Client ID - numbers
#Area (region of the world) - Drop Down list with restriction
#Nationality - Drop Down List with restriction (based on the area selection, the list is defined)
#E-mail (@)
#Date of enquiry (when did the client contacted us) - Date only
#Date of handled requiry (when did we handled the request from the client) - Date only
#Date of final handling (in some rare case, we need to ask the client to send us some documents to complete his request) - Date only
#Status - Drop Down List with restriction
#Employee ID - user who has entered the entry - drop down list

There are two challenging parts in my opinion



First the Nationality is defined by the previous Area selection
Second, the 3 dates column which I think can be improved and I need your suggestion

How many table should I create for my database?

Thank you ALL!

peace

[davegri]

Table for services (your main table)
Table for Clients (especially if same client has many requests or you have many clients)
Table for Employees
Table for Nationality

[orange]

I think you should give us a 5 line overview of the purpose of the database. More specifically, an overview of the Business that this proposed database is intended to support.

I see Clients, Employees, GeographicArea, Nationality, Enquiries, Enquiry Processing with Dates, EnquiryStatus, but do not know how these relate to one another.
I also see Enquiry/Requiry and Request which may be the same thing. There is a potential for Documents also.

A clear description of "a day at the office" might tie all these concepts together.

Good luck with your project.

[Myself2019]

Thank you for the reply. I really appreciate it.

The purpose of this database is to have a record of ALL the deleted accounts. We are a small team of 10 people who will have access to this database - each of us has a unique employee ID (it doesn't matter if we enter it manually via a dropdown list)

#ID - numbers - primary key
#Client ID - numbers - unique customer ID
#Area (region of the world) - Drop Down list with restriction - the idea is to make reports based on the area and nationality
#Nationality - Drop Down List with restriction (based on the area selection, the list is defined)
#E-mail (@)
#Date of enquiry (when did the client contacted us) - Date only
#Date of handled requiry (when did we handled the request from the client) - Date only
#Date of final handling (in some rare case, we need to ask the client to send us some documents to complete his request) - Date only
#Status - Drop Down List with restriction
#Employee ID - user who has entered the entry - drop down list

Does it clarify my request?

[orange]

A little.

Customers have Accounts.

The purpose of this database is to have a record of ALL the deleted accounts.

Why? Would you actually delete account info? Should you keep all of the info and have a flag/indicator that XX account is no longer active?

As for Access, field names should not have embedded spaces or special characters. Use alphabetic and numeric chars and optionally the underscore "_" only.

Good luck with your project.

[Myself2019]

Thanks for your reply
I would say that the purpose is more to keep a record of the deactivated account.
So How many table should I create?