The internal column count that Microsoft Access uses to track the number of fields in the table has reached 255, even though you may have fewer than 255 fields in the table. This can happen because Access does not change the internal column count when you delete a field. Access also creates a new field (increasing the internal column count by 1) for every field whose properties you modify.
It's a database of schools, providing education from pre - reception - FE/HE (15 years) with 6 infectious diseases. (so, y1a,y1b,y1c,y1d,y1e,y1f x15).
Some schools offer different age ranges of education provision.
I guess one way of doing it is to rearrange the data into a tidier format making it long instead of wide. But that's a massive faff for a project that may not move along much further....
Here we go:
https://support.microsoft.com/en-gb/help/291556/you-receive-a-too-many-fields-defined-error-message-when-you-save-a-ta
The internal column count that Microsoft Access uses to track the number of fields in the table has reached 255, even though you may have fewer than 255 fields in the table. This can happen because Access does not change the internal column count when you delete a field. Access also creates a new field (increasing the internal column count by 1) for every field whose properties you modify.
I have reached > 255 with 157 + 157 right?
This suggests a way of doing it with 3
https://stackoverflow.com/questions/13846776/union-all-query-too-many-fields-defined
Obvious question:
Why have I got 157 fields?
It's a database of schools, providing education from pre - reception - FE/HE (15 years) with 6 infectious diseases. (so, y1a,y1b,y1c,y1d,y1e,y1f x15).
Some schools offer different age ranges of education provision.
I guess one way of doing it is to rearrange the data into a tidier format making it long instead of wide. But that's a massive faff for a project that may not move along much further....