Recent content by thomer

Yep, how it pops out unfortunately... and that fixed it. Thanks!

When I run the query it gives me a pop-up asking me to enter the value for Q1 and Q2. Actual SQL query below: SELECT Responses.Status, Responses.[Internal ID], Responses.[Created At], Responses.[(storenum)], Responses.[(role)], Responses.[(month)], Responses.[(SQ1)], Responses.[(SQ2)]...

Where would I insert that into the SQL query I copied above (sorry, complete scrub at this). Thanks!

I'm probably not going to normalize it right off the bat (mostly because I'm still finding out how I want to cut/analyze the data) so how would I structure the query to do it the tedious way (if I'm looking across a single record to see how many times "Red" is used - per my first comment). Thanks.

Is that how to normalize it or how I would set it up to do the IIf(Field1 = "Red", 1, 0) + IIf(Field2 = "Red", 1, 0) idea?

So really quick (because I literally know nothing about Access) - how would I structure my query if I don't normalize the data (query so far below): SELECT Responses.Status, Responses.[ID], Responses.[Create], Responses.[(F1)], Responses.[(F2)], Responses.[(F3)], Responses.[(Q1)]...

I'd rather normalize it but I don't know enough about Access to know if it's really worth the trouble it to do so every time I update the database (several times a week).

The one issue with normalizing it is that I'm generating about 3000-4000 records a month and each has about 80 fields (so it would be a lot of individual records for Access to handle very quickly). I'm also effectively doing some analysis on it across a record, and across all records for that...

Very new to Access - I have a dataset that unfortunately is structured where an individual item is across one record (eg one record = one row with a number of columns) and it isn't feasible to restructure it into a more database friendly format prior to being brought into Access. I'm looking to...