Normalised database from a broken spreadsheet
Deliverable: A real flat sheet with repeated data, redesigned into normalised tables with keys and relationships, imported and verified so no records are lost in the move.
Course
Database work for the office — designing tables that hold up, querying them properly, and building forms and reports colleagues can use without breaking anything.
6 modules · 6 weeks
Deliverable: A real flat sheet with repeated data, redesigned into normalised tables with keys and relationships, imported and verified so no records are lost in the move.
Deliverable: A form with a subform for related records, lookup-driven combo boxes and validation that refuses incomplete entries with a message a colleague can act on.
Deliverable: A report grouped and totalled at two levels, formatted to print cleanly and export to PDF, driven by a parameter query the user supplies at run time.
Every student gets placement assistance — that is what 100% placement assistance means. It is support for all, not a job for all. We do not promise a specific salary, a specific number of interviews, or placement at any named company, and you should be wary of anyone who does.
Almost everyone arrives with the same file: one sheet, thousands of rows, and the customer’s name and address retyped on every single line.
It works until the customer moves. Then it is in there four hundred times, three hundred and eighty of them get updated, and no report agrees with any other report again. That is not carelessness — it is what happens when related data is forced into a flat grid.
Access stores each fact once and links to it. The first two modules are about making that move properly, using a real messy sheet rather than a tidy example.
Most Access databases that become unusable were badly designed on day one and patched afterwards.
So normalisation comes before queries, forms or reports, and it is taught with an actual spreadsheet rather than abstractly. Get the tables right and the queries are straightforward, the forms almost design themselves, and a later migration to a proper server is a manageable job. Get them wrong and everything downstream is a workaround.
You can enter data straight into a table. Nobody else should.
The forms module exists because the person typing is usually not the person who built the database, and a well-made form is what stops a typo becoming a permanent record. Validation, lookups and error messages that say what is actually wrong are the difference between a database that stays clean and one that needs a rescue in six months.
There is a real ceiling — file size, concurrent users, performance under load — and the last module gives you the actual numbers rather than a vague warning.
Knowing where that line is makes you more useful, not less. Recommending a departmental Access database where it genuinely fits, and recognising when the job needs MySQL or SQL Server instead, is a judgement most offices are short of.
Questions
When your data has relationships — customers who have many orders, students who have many marks — and a spreadsheet is forcing you to repeat the same values on every row. That repetition is where errors come from. Access stores each fact once and links to it, which is the whole reason the tool exists.
Widely, in small and mid-sized organisations, for exactly the jobs it suits — a departmental database that a few people share and nobody wants to buy a server for. It is not the right tool for a web application or a large multi-user system, and the last module is honest about where that line falls.
No, but they help each other. Access has an SQL view behind every query, so you can build something visually and then read the SQL it generated, which is a gentle way in. If your goal is a data or developer role, take the SQL course as well — it targets the databases those roles actually use.
Then you migrate, and the course covers how to see it coming — file size limits, concurrent user limits and performance under load are all discussed with the numbers. A well-normalised Access database moves to MySQL or SQL Server far more easily than a badly designed one, which is another reason the design module comes early.
Three details is all we need. A course advisor will call you back.
SQL taught against a database big enough that a bad query is noticeably slow, because toy datasets hide performance entirely and performance is half of what the job tests.
The Excel that offices actually run on — lookup logic, PivotTables, Power Query pipelines, dashboards and enough VBA to automate the work you repeat every month.
Excel automation taught as programming rather than as macro recording, so the tools you build keep working when the data changes and somebody else opens the file.
The four applications every Indian office runs on, taught around the tasks you will actually be judged on rather than as a tour of every menu.
Next step
Tell us what you want to learn and we will help you pick the right course, batch and mode.