What information do you know about the table? Is it always three responses for each user, or will that vary (is there a max number of responses/data units)? and how large of a table are we talking about....100 row table, or 100,000 row table? Also, are the response fields predictable values, such as Response1, response2, etc. or are they different for each record? Finally, is this something you will need to reuse over and over?There are currently 11 responses for each user but only 8 are required fields. I could make all of them required to aid in the predictability of the table. I am anticipating around the 100 user range, so that gives a table of approximately 1000 rows.The responses can be placed into 11 columns based on the QuestionID being asked. QuestionID is a field of the existing table that could be used to help sort responses into like columns.This query will be executed each time a webpage loads, to refresh the data in case new entries have been made since the last visit, so, yes, it will be used often.To give you some idea how the answers might affect things....you can do a join on a single table, and if for instance you knew you only had three responses to deal with, you could write a query (an ugly one mind you....but hey if it works )that would join the table to itself three times, and could populate the fields correctly. If the number of possible responses is unknown, then that idea goes out the door.Does this get too ugly when we talk of 11 responses? I thought of something like this, but didn't know how to write the query.If the number of rows in the table is low....I would personally suggest just try to manually fix the problem.Can't do this, because then I would have to rewrite the DNN module that is generating and reading from the existing table. Ugh!Oh, forgot to ask, what kind of SQL are you running...MS SQL, Access, Oracle, MySQL, or something else?MS SQL 2000I still do not know exactly how this can be done, but since you are being flexible and not trying to do all of this in one query, I can try to be flexible too and think on it for a while and see what I can come up with.I really appreciate your input. Thanks a bunch and I hope I'm explaining things accurately. SQL queries are not my expertise.Joel