J
Jaazaniah
I have a scheduling table (tblHistory), and it contains date of
transaction, and references to relevant information such as room and
client. I can query a view of the schedule to include nulls in the
history to show the proverbial negative, but now I'm nearly done with
this project with one notable exception.
The old scheduling view included 3 columns of client information for
simultaneous events. These 3 columns all share the same room
designation in the database, but are subdivided rooms in real life. It
also included 2 columns for rooms other than the subdivided room.
My main question is how would you either:
Render columns of a subreport up to X iterations while being flexible
enough to allow for multiple records.
OR
Generate multiple null room details for each situation outlined above
(I can carry date/time grouping given nulls) so the report renders
them normally? I couldn't think of how to structure a query to do it.
OR
Should I be looking at enforcing a new standard for the scheduling
sheets?
transaction, and references to relevant information such as room and
client. I can query a view of the schedule to include nulls in the
history to show the proverbial negative, but now I'm nearly done with
this project with one notable exception.
The old scheduling view included 3 columns of client information for
simultaneous events. These 3 columns all share the same room
designation in the database, but are subdivided rooms in real life. It
also included 2 columns for rooms other than the subdivided room.
My main question is how would you either:
Render columns of a subreport up to X iterations while being flexible
enough to allow for multiple records.
OR
Generate multiple null room details for each situation outlined above
(I can carry date/time grouping given nulls) so the report renders
them normally? I couldn't think of how to structure a query to do it.
OR
Should I be looking at enforcing a new standard for the scheduling
sheets?