CMST 100F at the University of Maryland Global Campus introduces database systems and teaches you to build a small, professional database.
UMGC describes it as an introduction to database systems, their terminology and the principles of database management. The goal is to use database management applications effectively to create professional databases.
Topics include how best to organize, manage and access stored data, how to protect databases and how to extract useful information. Hands-on practice with industry-standard database software is provided, and it is worth 1 credit.
It is not open to students who have completed CMST 303, and you can receive credit for only one of CAPP 100F, CAPP 103, CMST 100F or CMST 103. Of the CMST 100 modules, this is the one most students find hardest, because a poor table design causes problems everywhere else.
Course at a Glance
| Item | Details |
|---|---|
| University | University of Maryland Global Campus (UMGC) |
| Course code | CMST 100F |
| Credits | 1 |
| Restrictions | Not open to students who have completed CMST 303 |
| Credit overlap | Only one of CAPP 100F, CAPP 103, CMST 100F or CMST 103 |
| Typical work | Hands-on database projects with tables, queries, forms and reports |
What CMST 100F Covers
| Topic (UMGC) | What it means in practice |
|---|---|
| Terminology and principles | Tables, records, fields, primary keys and relationships |
| Organizing and managing data | Designing tables so each fact is stored once |
| Accessing stored data | Queries, forms and sorting or filtering |
| Protecting databases | Validation rules, backups and access control |
| Extracting useful information | Queries with criteria, calculations and reports |
Key Concepts Explained
Primary and Foreign Keys
A primary key uniquely identifies each record. A foreign key in another table stores that value to link the two, creating a relationship.
Example: A Customers table has CustomerID as its primary key. An Orders table includes CustomerID as a foreign key, so each order links to one customer, and one customer can have many orders (a one-to-many relationship).
Store Each Fact Once
Repeating the same data in many records wastes space and causes errors when it changes. Splitting it into its own table fixes this.
Example: If each order record repeats the customer's address, a customer who moves needs every order updated. Keeping the address only in Customers means one change updates every order view.
Query Criteria
Queries pull the records you need. Criteria on the same row combine with AND; criteria on separate rows combine with OR.
Example: To find orders over $500 placed in 2026, put ">500" under OrderTotal and a 2026 date range under OrderDate on the same criteria row.
Protecting Data and Getting Information Out
UMGC lists protecting databases and extracting useful information as course topics, so expect tasks on both. Common protection features include required fields, validation rules (for example, a quantity must be greater than zero), input masks for phone numbers or dates, and regular backups.
Enforcing referential integrity on relationships stops orders being created for customers who do not exist.
To extract information, combine queries with calculated fields and grouping, then present results in a report with clear headings, totals and sensible sorting.
Typical Assignments and How to Approach Them
| Assignment type | What it tests | How to approach it |
|---|---|---|
| Table design | Fields, data types, keys | Plan tables on paper first |
| Relationships | Linking tables | Enforce referential integrity |
| Queries | Criteria and calculations | Test with records you know should appear |
| Forms and reports | Presenting data | Group, sort and total sensibly |
Designing Forms and Reports
Forms are how people enter data; reports are how they read it. Both should suit the user, not just display every field.
- Order form fields in the sequence people naturally fill them in.
- Use drop-down lists for fields with fixed choices to prevent typing errors.
- Give reports a clear title, date, grouping and totals.
- Check reports in print preview so columns fit the page.
Example: A sales report grouped by region, sorted by salesperson, with a subtotal per region and a grand total at the end, answers the manager's questions at a glance. The same data as an unsorted list does not.
Where Students Get Stuck
- Mismatched data types. Linked fields must use matching types.
- Queries returning nothing. Check criteria rows (AND versus OR) and date formats.
- Everything in one table. Split repeating data into related tables.
- Software availability. Some database programs run only on certain operating systems; check requirements early.
Study Tips for CMST 100F
- Draw the tables and relationships before building anything.
- Name fields clearly and consistently, without spaces if possible.
- Enter a few test records to check each query.
- Back up your file before making big changes.
How We Help with CMST 100F
Send the instructions, any sample data, your database file and feedback. A tutor can explain design principles, fix and explain a query on a copy of your file, or prepare a model database for a comparable task.
GradeEssays is independent of the University of Maryland Global Campus. Our help is for learning; the work you submit must be your own under UMGC's academic integrity policy.
Build Your CMST 100F Database the Right Way
Share the instructions and your file. We explain table design, queries and reports with a working model.
Start My Database HelpFree revisions · Full refund if late · Written from scratch for your order
Frequently Asked Questions
It is a 1-credit course.
No. UMGC states it is not open to students who have completed CMST 303.
You can receive credit for only one of CAPP 100F, CAPP 103, CMST 100F or CMST 103.
UMGC describes industry-standard database software. Check your section's requirements, including operating system needs.
A field whose value uniquely identifies each record in a table.
Yes. We check criteria, joins and data types and explain the fix.