How to Create a Pivot Table in Microsoft Access
Why Stack Overflow recommends it
Stack Overflow users link it when answering questions about pivoting or cross-tabbing data in Access, since Access has no built-in PIVOT function and this shows the pivot table view as a workaround.
Recommended by 2 people across 2 different months, 2014 to 2018.
What it is
A 1.5 minute screencast from Howtech showing how to build a pivot table form in Microsoft Access. It walks through choosing the pivot table option under More Forms, opening the field list, and dragging fields into the row, column and data zones.
What people said
Recommends GolezTrol · 2014-12 · Stack Overflow · on “Group records and show each records value in one row”
Looks like you tried (did you?) to create a pivot table. This question [LINK] about the same subject might provide some insights, as might tutorials like this [LINK] or this [this video] .
Recommends Alex Yena · 2018-05 · Stack Overflow · on “Transposing or Pivoting in Access 2016”
As far as I know for now there are no PIVOT functions in access. But you can create pivot table based on existing one. In this video there is explained how [this video] Alternatively you will need IIF statement like this: Select [CustomerNo.], SUM(IIF([Month] ="Jan 18", [Quantity], 0 ) AS [Jan 18], SUM(IIF([Month] ="Feb 18", [Quantity], 0 ) AS [Feb 18], ...... SUM(IIF([Month] ="Last month", [Quantity], 0 ) AS [Last month] GROUP BY [CustomerNo.] Bad thing about it is you need update every month your script. If you will have better solutions I will be very thankful.
Cites Bacon Bits · 2015-01 · Stack Overflow · on “SQL payments matrix”
Your Payments table is de-normalized. Those date columns are repeating groups, meaning you've violated First Normal Form (1NF). It's especially difficult because your field names are actually data. As you've found, repeating groups are a complete pain in the ass when you want to relate the table to something else. This is why 1NF is so important, but knowing that doesn't solve your problem. You can normalize your data by creating a view that UNIONs your Payments table. Like so: CREATE VIEW NormalizedPayments (id, Year, Month, Amount) AS SELECT id, 2010 AS Year, 1 AS Month, 2010_01 AS Amount FROM Payments UNION ALL SELECT id, 2010 AS Year, 2 AS Month, 2010_02 AS Amount FROM Payments UNION ALL