Jump to content

KiwiKim25

Members
  • Posts

    11
  • Joined

  • Last visited

KiwiKim25's Achievements

Rookie

Rookie (2/14)

  • First Post
  • Collaborator
  • Conversation Starter
  • Week One Done
  • One Month Later

Recent Badges

0

Reputation

  1. There is a lot of other data in the portal. Sorry to keep being so vague about the rest of the info, but it's a work-restriction thing. After a lot of trial and error, it ended up working best for all involved to use the 2nd table. The program has been approved, works very well now and is in use. I just need to figure out this running tally. Thanks again for your help!
  2. The main table is a table of patients, and each record is a patient. Each patient has one ID number that is unique to them. The social table is a table of social information; one social history per patient/record (by ID number). The two tables are related directly by ID Number. The data I want to count/summarize is the intro/single/paired value, which is a single value per patient. There is other data on that table that is multiple per patient, but I don't need that counted up. Sorry I'm still figuring out how to explain the set up; Thank you for your patience with me!
  3. Sorry! I knew I was missing some info! The "Main Table" records are by the field "ID Number", like medical records. The "Active" field is a part of the "Main Table" (Main Table::Active). The "Main Table" and "Social Table" are related "ID Number = ID Number". My portal to the "Social Table" has the field for "social status", and hopefully below it a summary/count of all active records for each of the "Intro" "Single" and "Paired" values. I have the database set to sort on opening of "Main Table" to have the "Active" records shown first (and it works too!). We still need to access the non-active records from time to time but want to see the active ones first, so this works well for us.
  4. I have it all set up and working like a champ now. Thank you all for your help!
  5. Thanks to help in this forum, I'm almost done creating this database! I'm so excited! I've hit one last snag. Calculations/scripts are my downfall. Here is my dilemma: I have a "Main table". On it is a portal to my "Social Table". I am assigning each record a value of either "Intro" "Single" or "Paired" (which is in a "Social Status" field). Here's where I'm stuck. I need to do a count of how many records have the "Intro" value, "Single" value or "Paired" value, AND I need it to only count the records that also have the field/value "ACTIVE" selected (since we don't want to count non-active records). I made a field for the calculation, and have tried a variety of calculations, but am hitting the brick wall of my inability to do more than "Table::this = Table::that". Thoughts? Formulas/calculations/scripts to try? Thank you!!!!
  6. Ok, next snag, which is almost the same as the first. I have it set up so in the actions table I have a record for each type of action that can be take (once a day, twice a day, etc). Each record has the ID Number and a start and stop date. In my main table I have a portal to the actions table. I have an edit box to type in the actions taken (record) and enter the start and/or stop date. But I still need to have a summary on my main table that says what actions have a start date and no end date. The people using the database do not want to switch screens to look it up. They want it at a glance. How do I accomplish that? I really appreciate all the help. There is no one at my work available to ask these questions to. ~Kim~
  7. Huh, I knew I must be doing something odd. Thanks for bearing with me trying to make sense of my mess! Let me go try then and come back with my next snag. Thank you both very much!!
  8. Hm, I guess I don't understand still... I have a main table, each Person (ID number) has a record in that main table. I have a second table "Action", that is related by the field "ID number". People working with this data base will only be looking at the "Main Table". They don't want to have the whole history on the main table, but would like to see what is currently "active" or "not stopped yet". What I was doing was making a field for each action that could be taken (once a day, twice a day, etc) plus start/stop fields (dates). That's how I set up other tables, which are on the "main table" via portals. I'm not certain how to set this up so each 'action' is a record instead. Am I missing something basic here? Thanks again for helping me!
  9. I do have a related Actions table. I gave each action that can be taken it's own field. How can I filter it to only show the 'active' actions? Say Action 1 2 and 3 are currently active (started), but 4 5 and 6 have been stopped, what is the best way to have only the ones that haven't been stopped (1, 2, 3) show up? Each ID number can have multiple actions start and stop a number of times over the year, it's not just a one time thing. I'm probably just having a dumb moment, but I'm not finding that 'ah ha' moment just yet. Thanks for taking the time to help!!
  10. Help! I have no idea how to go about getting this 'idea' (demand) in place. I've attached a picture of what I need, to help with my poor explanation skills. I have what is essentially a medical record. For each ID number, there is a lot of things being entered. I'm stuck on one section. "Actions". I need to be able to state what day an action (once a day, twice a day, etc) was 'started' and 'stopped'. There can be more than one action active at one time. Each with it's own start and stop date. I need to keep a history of these start/stops (but not visible on the current table/portal). Also, the less typing the people entering the data have to do, the better (drop down menus, etc). I also need a "summary" of what is currently active. This means some sort of script that says shows fields that have a start date, but no end date containing a date newer than the last start date... or something along those lines. I'm feeling overwhelmed. Please help!!! ~Kim~
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.