{"id":38271,"date":"2026-04-13T15:12:57","date_gmt":"2026-04-13T08:12:57","guid":{"rendered":"https:\/\/times.edu.vn\/?p=38271"},"modified":"2026-05-08T18:00:22","modified_gmt":"2026-05-08T11:00:22","slug":"igcse-ict-database-tasks","status":"publish","type":"post","link":"https:\/\/times.edu.vn\/en\/igcse\/igcse-ict-database-tasks\/","title":{"rendered":"IGCSE ICT 0417 Database Tasks: 8-Step Strategy for Access (Paper 3) A*"},"content":{"rendered":"

IGCSE<\/a><\/strong>\u00a0ICT database tasks (ICT 0417)<\/strong>\u00a0are practical exam activities where you build and manipulate a relational database in software like Microsoft Access to produce precise outputs.<\/p>\n

You typically import CSV data, set correct data types and field properties, assign primary keys, create relationships using foreign keys, then run queries with sort and filter, validation rules, and wildcards.<\/p>\n

Marks come from accurate criteria logic, correct calculated fields, and professional reports, forms, and mail merge-ready datasets.<\/p>\n

Strong performance depends on avoiding structural mistakes and capturing clear evidence screenshots of table design, relationships, and query settings.<\/p>\n

A Step By Step Guide To IGCSE ICT Database Tasks<\/strong><\/h2>\n

\"IGCSE<\/p>\n

IGCSE ICT database tasks (ICT 0417) are practical marks in disguise. Examiners are not testing whether you \u201cknow Access\u201d; they are testing whether you can follow instructions precisely, build a clean relational database, and produce evidence that proves your method.<\/p>\n

Based on our years of practical tutoring at Times Edu, the fastest improvements come from system-thinking. You treat every task as a workflow: Import \u2192 structure \u2192 keys \u2192 relationships \u2192 queries \u2192 sort and filter \u2192 outputs (reports, mail merge, evidence).<\/p>\n

What IGCSE ICT database tasks usually include (Paper 2 \/ Paper 3)<\/strong><\/h3>\n

Students often revise \u201ctheory\u201d, then lose marks on execution. The practical database component is predictable, and the mark scheme rewards accuracy and completeness more than creativity.<\/p>\n\n\n\n\n\n\n\n\n\n\n\n\n
Exam action (typical)<\/strong><\/th>\nWhat the examiner is checking<\/strong><\/th>\nWhat loses marks<\/strong><\/th>\n<\/tr>\n
Import CSV and create tables<\/td>\nCorrect structure, correct data types, correct field names<\/td>\nWrong data type, truncated text, wrong field size<\/td>\n<\/tr>\n
Set a primary key<\/td>\nUniqueness and correct key choice<\/td>\nUsing a non-unique field, forgetting to set it<\/td>\n<\/tr>\n
Create relationships<\/td>\nRelational database logic, foreign key integrity<\/td>\nWrong fields linked, wrong join type, no evidence screenshot<\/td>\n<\/tr>\n
Build queries with criteria<\/td>\nCorrect filtering, correct operators, correct wildcards<\/td>\nCriteria in wrong row, AND\/OR confusion, wildcard misuse<\/td>\n<\/tr>\n
Sort and filter<\/td>\nControlled output ordering, correct subset<\/td>\nSorting wrong field, missing secondary sort<\/td>\n<\/tr>\n
Calculated fields<\/td>\nCorrect formula and formatting<\/td>\nWrong brackets, incorrect field names, wrong output format<\/td>\n<\/tr>\n
Reports \/ output<\/td>\nLayout accuracy and readability<\/td>\nMissing group\/sort, wrong fields, poor formatting<\/td>\n<\/tr>\n
Forms \/ data entry<\/td>\nUsability, field properties, validation<\/td>\nNo validation, wrong input masks, confusing layout<\/td>\n<\/tr>\n
Evidence screenshots<\/td>\nProof of method<\/td>\nScreenshots missing key settings or cropped<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

A critical detail most students overlook in the 2026 exam cycle is that marks are often awarded for \u201cprocess evidence\u201d even when the final output is close.<\/p>\n

If your evidence screenshots do not show the table design, relationships diagram, and query criteria clearly, you are donating marks.<\/p>\n

>>> Read more:<\/strong> IGCSE ICT vs Computer Science<\/a> 2026: What\u2019s the Difference and Which Should You Choose?<\/p>\n

Creating Relationships And Defining Data Types<\/strong><\/h2>\n

Step 1: Import data correctly (CSV \u2192 Table)<\/strong><\/h3>\n

In Microsoft Access, import is not a \u201cclick-next\u201d activity. You are making structural decisions that affect every later query.<\/p>\n

Use this checklist during import:<\/p>\n