Justin Lebar (starwiz@innovate-inc.com) writes:
> Sorry about the huge post, but I think this is the amount of
> information necessary for someone to help me with a good answer.

Yes, there was a whole lot of information, but I was not able to get
a complete understanding of what's going on. Probably because I'm too
impatient to go through it over and over again to get the pieces together.

There is a however a standard advice for this kind of problems. Namely,
in your posting include CREATE TABLE statements for the involved tables
(it may be a good idea to trim irrelevant columns), INSERT statements
with sample data and the desired output from that data. I realize that
in your case you may need to provide some 100-200 rows to get some
representative data. An alternative is put the data in comma-separated
files that can be bulk-loaded. Put any such files in an attachments, to
avoid line-wrap problems.

>hitid - the HitID of the user, taken from the session cookie. If there
>is no session cookie (for whatever reason), the HidID is written out
>as 0. While it wouldn't occur often, I can't guarantee that there will
>never be more than one response record attached to a singular hitid.

Not that I think it matters here, but I would store a NULL in HitID when
there is no hit id.

--
Erland Sommarskog, SQL Server MVP, sommar@algonet.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinf...2000/books.asp