Forums before death by AOL, social media and spammers... "We can't have nice things"
|    comp.databases.paradox    |    To crash or not to crash, asks Borland    |    9,834 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 8,898 of 9,834    |
|    Craig to All    |
|    How to set up a table    |
|    09 Nov 07 12:28:35    |
      From: craig.futterman@nospam.comcast.net              I am setting up some tables for data collection for a clincial study we are       conducting in our PICU.       The set up:       One of the data elements we are collecting is a sedation score. The problem       in hospitals is that the day starts @0700.       The key fields which attach this daughter table to the master are MRNumber       and DateOfOperation.       In this table I not only have that I have two other keys dayNumber (we are       collecting data for a max of 5 days) and timeofDay (we are collecting data       each hour). Of course, the last field is a non- keyed field called "Score".              The problem: All hospital personell work (& think) as the beginning of day 1       starts at 0700 and the last hour of day 1 is the next morning at 0600. Since       the data entry will be done by people who are not facile with computers, I       want the software to work like they think.       If I setup the key fields as above, Paradox will automatically reorder so       that midnight 0000 through 0600 will come before 0700 through 2300.              I was thinking about adding the hour # to the hour such as 1-0700, 2-800,       3-0900 though 24-0600 as a string for that key field. What do you guru's       think?              Thanks in advance,              Craig              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca