Jump to content

StephenG57

Members
  • Content Count

    10
  • Joined

  • Last visited

Community Reputation

0 Neutral

About StephenG57

  • Rank
    novice
  • Birthday September 24
  1. StephenG57

    Checkbox Form

    Thank you very much for your response Fenton. Right now, the powers at be are fairly adamant in using the checkbox format, but I think your side by side portal idea will work the best when I have time to provide them with a working model similar in appearance to their current comfort level. As such, for the interum, I have constructed medications list, chart_record and link them using a meds_join file. Very similar to the inventory program setup. To overcome the checkbox issue, I have used a script button at the bottom of the page which "posts" the results of the checkbox choices into the meds_join file. It utilizes ValueCount and MiddleValues to translate the arrayed entries into individual join_file records. Again, more complexity than I like, but it works and they seem happy with the result. More importantly, it will still allow me to harvest data from the meds_join file for reports. Again, you have helped me immensely with pointing out the many different approaches to "skinning this cat", and I'm sure as i learn more about 7, I will utilize many of your suggestions. Thanks!
  2. StephenG57

    Checkbox Form

    Thank you very much for your response Fenton. Right now, the powers at be are fairly adamant in using the checkbox format, but I think your side by side portal idea will work the best when I have time to provide them with a working model similar in appearance to their current comfort level. As such, for the interum, I have constructed medications list, chart_record and link them using a meds_join file. Very similar to the inventory program setup. To overcome the checkbox issue, I have used a script button at the bottom of the page which "posts" the results of the checkbox choices into the meds_join file. It utilizes ValueCount and MiddleValues to translate the arrayed entries into individual join_file records. Again, more complexity than I like, but it works and they seem happy with the result. More importantly, it will still allow me to harvest data from the meds_join file for reports. Again, you have helped me immensely with pointing out the many different approaches to "skinning this cat", and I'm sure as i learn more about 7, I will utilize many of your suggestions. Thanks!
  3. StephenG57

    Checkbox Form

    Thank you very much for your response Fenton. Right now, the powers at be are fairly adamant in using the checkbox format, but I think your side by side portal idea will work the best when I have time to provide them with a working model similar in appearance to their current comfort level. As such, for the interum, I have constructed medications list, chart_record and link them using a meds_join file. Very similar to the inventory program setup. To overcome the checkbox issue, I have used a script button at the bottom of the page which "posts" the results of the checkbox choices into the meds_join file. It utilizes ValueCount and MiddleValues to translate the arrayed entries into individual join_file records. Again, more complexity than I like, but it works and they seem happy with the result. More importantly, it will still allow me to harvest data from the meds_join file for reports. Again, you have helped me immensely with pointing out the many different approaches to "skinning this cat", and I'm sure as i learn more about 7, I will utilize many of your suggestions. Thanks!
  4. StephenG57

    Checkbox Form

    I am in the process of designing a medications list database for my office, one where we can record a patient's list of medications they are taking during their check in process. One key to this design will be ease of use. I know that I could use an inventory-like setup, whereby I would have a table labeled med_chart (similar to a purchase order set up). Utlizing a med_join file portal on the med_chart table, it would pull information from a continually updated medications table of products used. I have presented this, and although it works, the nurses find it very cumbersome. Instead of a portal where they use individual entries to generate their chart of meds for a particular patient, they would like to have me design a one page form in checkbox format listing all the medications. They would simply check the boxes of the medications to generate their chart record. I could do that with a simple flat file, but we're talking 100's of medications in the one table, of which would have to include in Case/Replace calculations making this too cumbersome...for them and for me. I guess what I'm asking, is using a checkbox form to generate join file entries possible? Are there any articles or examples where this is done that I could study? Or should I just simply stick with the portal format and hope this data entry will not greatly impede their check in process? I'm stuck...thanks in advance for your response.
  5. StephenG57

    Checkbox Form

    I am in the process of designing a medications list database for my office, one where we can record a patient's list of medications they are taking during their check in process. One key to this design will be ease of use. I know that I could use an inventory-like setup, whereby I would have a table labeled med_chart (similar to a purchase order set up). Utlizing a med_join file portal on the med_chart table, it would pull information from a continually updated medications table of products used. I have presented this, and although it works, the nurses find it very cumbersome. Instead of a portal where they use individual entries to generate their chart of meds for a particular patient, they would like to have me design a one page form in checkbox format listing all the medications. They would simply check the boxes of the medications to generate their chart record. I could do that with a simple flat file, but we're talking 100's of medications in the one table, of which would have to include in Case/Replace calculations making this too cumbersome...for them and for me. I guess what I'm asking, is using a checkbox form to generate join file entries possible? Are there any articles or examples where this is done that I could study? Or should I just simply stick with the portal format and hope this data entry will not greatly impede their check in process? I'm stuck...thanks in advance for your response.
  6. StephenG57

    Checkbox Form

    I am in the process of designing a medications list database for my office, one where we can record a patient's list of medications they are taking during their check in process. One key to this design will be ease of use. I know that I could use an inventory-like setup, whereby I would have a table labeled med_chart (similar to a purchase order set up). Utlizing a med_join file portal on the med_chart table, it would pull information from a continually updated medications table of products used. I have presented this, and although it works, the nurses find it very cumbersome. Instead of a portal where they use individual entries to generate their chart of meds for a particular patient, they would like to have me design a one page form in checkbox format listing all the medications. They would simply check the boxes of the medications to generate their chart record. I could do that with a simple flat file, but we're talking 100's of medications in the one table, of which would have to include in Case/Replace calculations making this too cumbersome...for them and for me. I guess what I'm asking, is using a checkbox form to generate join file entries possible? Are there any articles or examples where this is done that I could study? Or should I just simply stick with the portal format and hope this data entry will not greatly impede their check in process? I'm stuck...thanks in advance for your response.
  7. StephenG57

    Need Opinions

    First some background. I have been using Filemaker for about 5 years, mainly for solution development at work. These various databases are in version 6, shared over a company network using Server version 5.5. Due to the purchase date on our license, we received a free upgrade to Server 7 and Pro 7 licenses. Current problem: I have an XServe (running 10.2.8) that I would like to host a web based registration database on for an upcoming school reunion. I would like to be able to have classmates update their contact/registration information without my need to post this information manually. I would like to do this with Filemaker. Problem is, I don't have Server 7 Advanced...I only have Server 7 and the Pro 7 available to use for this project. I have discovered that on the XServe, Pro 7 cannot load the web sharing plug in...and Server 7 has no web publishing capabilities. I really don't want to shell out the $$$ to upgrade my license to Server 7 Advanced, nor do I want to tie up a separate client running Pro 7 to IWP this database. Any suggestions?
  8. StephenG57

    Is this a join file question?

    I have set up a field called "prod_category" in which I can categorize all of the different products (ie: frames, lenses, contacts...)so data entry can be made in different layouts displaying category specific variables. I then set up value lists based on different relationships such as you suggested...it works great. Thanks.
  9. StephenG57

    Is this a join file question?

    After going ahead and working with one Products database, I basically came to the same conclusion. While there are multiple fields for multiple products that I find necessary to differentiate, many of the miscellaneous products will suffice with a concatenated specifications field. Thanks so much for the suggestion.
  10. StephenG57

    Is this a join file question?

    I have somewhat of the same situation I'm struggling with at work. I am trying to implement an Inventory database for an optical shop. Because we deal with many different products (frames, blank lenses, contacts, pharmaceuticals, misc. parts), all with different variables (ie: frames [male/female, material, color, size, etc.], blank lens [size, material, power, base curve, etc.], I thought of making separate databases for each category of product. But, after trying to link all of these together in a join file, I've come to the conclusion that I would just be better off with one (somewhat massive) PRODUCTS database containing all the different variables that could join with my PO and Invoice files through a line item file. While the PRODUCTS database will get somewhat "crowded" with records, I have found no way to have these separate while still maintaing PO and Invoice relationships (and my sanity). Any thoughts?
×

Important Information

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