Databases
StackOverflow2013
Postsdbo
POCross Tab - Storing different dates (Meeting1, Meeting2, Meeting 3 etc) in the same column
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POCross Tab - Storing different dates (Meeting1, Meeting2, Meeting 3 etc) in the same column
    primarykey
    data
    text
    <p>I need to keep track of different dates (dynamic). So for a specific Task you could have X number of dates to track (for example DDR1 meeting date, DDR2 meeting date, Due Date, etc).</p> <p>My strategy was to create one table (DateTypeID, DateDescription) which would store the description of each date. Then I could create the main table (ID, TaskDescription, DateTypeID). So all the dates would be in one column and you could tell what that date represents by looking at the TypeID. The problem is displaying it in a grid. I know I should use a cross tab query, but i cannot get it to work. For example, I use a Case statement in SQL Server 2000 to pivot the table over so that each column name is the name of the date type. IF we have the following tables:</p> <p><strong>DateType Table</strong></p> <h2>DateTypeID | DateDescription</h2> <pre><code> 1 | DDR1 2 | DDR2 3 | DueDate </code></pre> <p><br> <strong>Tasks Table</strong></p> <h2>ID | TaskDescription</h2> <pre><code>1 | Create Design 2 | Submit Paperwork </code></pre> <p><br> <strong>Tasks_DateType Table</strong></p> <h2>TasksID | DateTypeID | Date</h2> <pre><code>1 | 1 | 09/09/2009 1 | 2 | 10/10/2009 2 | 1 | 11/11/2009 2 | 3 | 12/12/2009 </code></pre> <p><br> THE RESULT SHOULD BE:</p> <h2>TaskDescription | DDr1 | DDR2 | DueDate</h2> <pre><code>Create Design |09/09/2009 | 10/10/2009 | null Submit Paperwork |11/11/2009 | null | 12/12/2009 </code></pre> <p>IF anyone has any idea how I can go about researching this, I appreciate it. The reason I do this instead of making a column for each date, has to do with the ability to let the user in the future add as many dates as they want without having to manually add columns to the table and editing html code. This also allows simple code for comparing dates or show upcoming tasks by their type (ex. 'Create design's DDR1 date is coming up' ) If anyone can point me in the right direction, I appreciate it.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USOMG Ponies
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POCross Tab - Storing different dates (Meeting1, Meeting2, Meeting 3 etc) in the same column
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POCross Tab - Storing different dates (Meeting1, Meeting2, Meeting 3 etc) in the same column
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POCross Tab - Storing different dates (Meeting1, Meeting2, Meeting 3 etc) in the same column
      1. USMNZ
      1. VTFavorite
    1. COwhich version of sql server?
      singulars
      1. POCross Tab - Storing different dates (Meeting1, Meeting2, Meeting 3 etc) in the same column
      1. USNathan Koop
    2. COSQL 2000.. but I can translate TSQL from 2005 to 2000 just fine. I just need some help in finding the right direction.
      singulars
      1. POCross Tab - Storing different dates (Meeting1, Meeting2, Meeting 3 etc) in the same column
      1. This table or related slice is empty.
    3. COThank you ALL for the help. Really appreciate every single post.
      singulars
      1. POCross Tab - Storing different dates (Meeting1, Meeting2, Meeting 3 etc) in the same column
      1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload