You are looking for best practices in dealing with data is denormalized. I get that you have done this via dynamic cross tab but there isn't really a normal way of handling this. The best chance is the coalesce. An even better place in the process is to get your data the way you want it when you crosstab it initially.
This what i was looking for.
What you posted is not a dataset. Nobody can load that into a table without first writing all the insert statements and create table statements. Keep in mind that we are all volunteers around here. When you don't post stuff in a consumable format the best anybody can do is take a shot in the dark.
Your post that contained your solution sounded very much like you wanted help with a better approach. You included selecting from a view (that we don't have), then updating a table (that we don't have). It seems that you want a magical solution to a problem without providing the details needed to solve it.
i didn't need nor want a specific solution to this 'data', and the 'data' was and 'example set', and not a 'working set'. i was indeed looking for a more 'patterned' approach to do this, more of a WAY to solve this type of problem rather than the supposed 'magical' fix.
Apparently, i was already doing it.
the iterative approach through the columns works, and does indeed allow me to generate the YRQStart (first occurance column), because of this iterative approach.... but dang it it uses a cursor, and anytime anyone uses a cursor... i hear a 'it should be a set based approach'.
i am unclear how i can clear that point up, if you would like to expound on it?