0
Add your answer:
Earn +20 pts
What is a field that might be used in a database about students?
A field that might be used in a database about students is "student ID," which is a unique identifier for each student in the database.
What would a librarian use a database for?
A librarian would use a database to organize and store information about the library's collection, such as book titles, authors, publication dates, and availability. This helps the librarian manage the library's resources more effectively and assist patrons in finding the materials they need. Additionally, databases can support cataloging, circulation, and reference services within the library.
What would a developer of a relational database call a record?
A developer of a relational database would call a record a "row" in database terminology. This term typically refers to a single entry in a database table that contains a set of related data fields.
What is the fingerprint database called?
I would assume it was a relational database.. I also assume you mean the fingerprint database that is used by the police forces. as far as i am aware it is a relational database. I think because you could query either a name or a fingerprint reading and then get the information relating to it..Example: If you were looking for the name to a set of fingerprints, you would enter the finger print into your query, and then you might get a name if it is in the database, and if you were looking for the fingerprints to a guy, you would enter a name and you might get the fingerprints for him if you have the right name and it is contained within the database.
Are all the records in a database stored in a field?
No, records in a database are stored in tables, a field is a specific piece of data within a record. Each record in a table contains multiple fields, each representing a different attribute of the data being stored.
What fields would a doctor surgery might be in the database?
some of the fields a doctor surgery database would have are:Patient ID numberfirst namelast namehouse number/namestreet namecity/townpost codedoctors last name
What is a field that might be used in a database about students?
A field that might be used in a database about students is "student ID," which is a unique identifier for each student in the database.
What are the fields that you would expect to find in a database for a shop selling computer games?
List the fields that you would expect to find in a database for a shop selling computer games.
What is an example of a field that might be used in a database about librarians?
the name of the book or the name of the librarian it depends if you mean the library in which case it would be the book title or if your talking about the actual llibrarian then it would be something like their name, age and address
What type of application would you use to store data in an organized manner using fields and records?
Database
What database fields would be the most suitable to use as a primary key Student Name?
It is recommended to use a unique identifier such as a student ID number as a primary key instead of the student name. This is because names are not always unique and can change, while an ID is a reliable and stable way to uniquely identify each student's record in the database.
Why do you need common fields in a database?
A common field is a field of data that is shared among all forms in a database. Without them, it would be difficult and/or time-consuming to create other forms.
What is a field in a database that contains formulas or functions in Excel?
In a database a field with a formula is called a calculated field. A calculated field should actually be in a table, as it can be calculated from data in other fields in the table, so it normally only appears in queries, reports and forms. In a spreadsheet it would just be a calculation.
Where can one find a large database of stock photos?
A local office supply store might have large database of stock photos but there would probably be a charge. There are other places where one might locate a large database of stock photos but this would require some research.
Why do you require a RegNo field in MS-access when you already have RollNo field?
That question cannot really be answered, as it is down to the data you have and the database you are trying to design. You may well need these fields and have one as a primary key and have another field unique. To properly design a database, a lot of thought has to go into it, especially if there is more than one table and there are relationships. Even for one table you would work out what fields you need and how you design them. So you may have a requirement for both of those fields. It is your design, not Access itself, that decides what fields you need.That question cannot really be answered, as it is down to the data you have and the database you are trying to design. You may well need these fields and have one as a primary key and have another field unique. To properly design a database, a lot of thought has to go into it, especially if there is more than one table and there are relationships. Even for one table you would work out what fields you need and how you design them. So you may have a requirement for both of those fields. It is your design, not Access itself, that decides what fields you need.That question cannot really be answered, as it is down to the data you have and the database you are trying to design. You may well need these fields and have one as a primary key and have another field unique. To properly design a database, a lot of thought has to go into it, especially if there is more than one table and there are relationships. Even for one table you would work out what fields you need and how you design them. So you may have a requirement for both of those fields. It is your design, not Access itself, that decides what fields you need.That question cannot really be answered, as it is down to the data you have and the database you are trying to design. You may well need these fields and have one as a primary key and have another field unique. To properly design a database, a lot of thought has to go into it, especially if there is more than one table and there are relationships. Even for one table you would work out what fields you need and how you design them. So you may have a requirement for both of those fields. It is your design, not Access itself, that decides what fields you need.That question cannot really be answered, as it is down to the data you have and the database you are trying to design. You may well need these fields and have one as a primary key and have another field unique. To properly design a database, a lot of thought has to go into it, especially if there is more than one table and there are relationships. Even for one table you would work out what fields you need and how you design them. So you may have a requirement for both of those fields. It is your design, not Access itself, that decides what fields you need.That question cannot really be answered, as it is down to the data you have and the database you are trying to design. You may well need these fields and have one as a primary key and have another field unique. To properly design a database, a lot of thought has to go into it, especially if there is more than one table and there are relationships. Even for one table you would work out what fields you need and how you design them. So you may have a requirement for both of those fields. It is your design, not Access itself, that decides what fields you need.That question cannot really be answered, as it is down to the data you have and the database you are trying to design. You may well need these fields and have one as a primary key and have another field unique. To properly design a database, a lot of thought has to go into it, especially if there is more than one table and there are relationships. Even for one table you would work out what fields you need and how you design them. So you may have a requirement for both of those fields. It is your design, not Access itself, that decides what fields you need.That question cannot really be answered, as it is down to the data you have and the database you are trying to design. You may well need these fields and have one as a primary key and have another field unique. To properly design a database, a lot of thought has to go into it, especially if there is more than one table and there are relationships. Even for one table you would work out what fields you need and how you design them. So you may have a requirement for both of those fields. It is your design, not Access itself, that decides what fields you need.That question cannot really be answered, as it is down to the data you have and the database you are trying to design. You may well need these fields and have one as a primary key and have another field unique. To properly design a database, a lot of thought has to go into it, especially if there is more than one table and there are relationships. Even for one table you would work out what fields you need and how you design them. So you may have a requirement for both of those fields. It is your design, not Access itself, that decides what fields you need.That question cannot really be answered, as it is down to the data you have and the database you are trying to design. You may well need these fields and have one as a primary key and have another field unique. To properly design a database, a lot of thought has to go into it, especially if there is more than one table and there are relationships. Even for one table you would work out what fields you need and how you design them. So you may have a requirement for both of those fields. It is your design, not Access itself, that decides what fields you need.That question cannot really be answered, as it is down to the data you have and the database you are trying to design. You may well need these fields and have one as a primary key and have another field unique. To properly design a database, a lot of thought has to go into it, especially if there is more than one table and there are relationships. Even for one table you would work out what fields you need and how you design them. So you may have a requirement for both of those fields. It is your design, not Access itself, that decides what fields you need.
Is relational database better than manual database?
It really depends on the purpose of the database. For some function relational would be better, for some manual would be. You might want to research the application you wish to incorporate.
When would you use a database program?
when i need to see table relationships and sort data by custom fields
