Jump to content

GarthT

Members
  • Content Count

    48
  • Joined

  • Last visited

Community Reputation

0 Neutral

About GarthT

  • Rank
    novice
  • Birthday March 10

FileMaker Experience

  • Skill Level
    Novice
  • FM Application
    16 Advanced

Platform Environment

  • OS Platform
    Mac
  • OS Version
    High Sierra

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Thanks Steve, I understand the analogy. The actual database (now) attached makes your method difficult to implement (I think!) ProcedureEvent (The surgical operation in normal language) as well as being the child of Patient and the parent of PrimaryProcedureEvent is also the parent of RepairEvent, SurgeonEvent, PathologyEvent, AntibioticEvent and ComplicationEvent. The ProcedureEvent form is where I envisage putting most of my data into the database. This seems to work well using a series of portals. I have moved some of the fields out of ProcedureEvent into RepairEvent - similar to your suggestion I have left some of the attributes (height, weight, BMI etc) in the ProcedureEvent table rather than moving them to the patient table as they are those measurements at the time of the ProcedureEvent and they could be different for different ProcedureEvents - hope that makes sense. On the Patient form I have set up a series of tabbed reports containing portals to summarise (and create some parts of) Referrals, Reviews, Comorbidities and Pathology. These all work well. I plan to make the black boxes a button to jump to the full forms The problem I am having is that Procedures (PrimaryProcedureEvent) can have more than one value for a given date, and they do not show in the portal. Any more thoughts? ! Plionidal solution 2017.fmp12 Thanks Lee I have downloaded the first file - it looks difficult - I am not sure I am up to three coffee cups! The second link is broken G
  2. Hi I am trying to set up a database to review some surgical cases of mine. The basic structure seems to work fine. I have attached an abridged section of the database with four tables: Patient --< ProcedureEvent --< PrimaryProcedureEvent >-- PrimaryProcedure What I would like to do is: When looking at the Patient layout (Grandparent) be able to see a summary of all of the Primary Procedure Events (Grandchildren). The attached file has some text dummy data on the Patient layout to show what I am trying to achieve. I have tried using portals bu I can only get the first "Grandchild" to show Thanks for any advice and help Garth Parent_Child_Grandchildren.fmp12
  3. Thanks Somehow it seemed conceptually wrong for the Topic to be the Parent - as the question is the "main event" I think I just need someone to tell me that was OK for it to be the child even though it is the meat of the project!! OK - I think if I use the relationship in the correct way everything else should fall into place. I will get it a go cheers Thanks again Comment I think it now works Value List technique after Comment.fmp12
  4. Hello I am trying to create solution for examination questions. Each question can be allocated to one of 38 key topics and only one of 38 topics I have decided to do this using a value list based on a table of Key topics Each Key Topic has a name and a code (an alphanumeric value) In the Question layout I want to have a drop down menu to chose the Key Topic and have the code auto-populate using a related field. I am struggling to understand the relationship because the Question seems to be the parent in the relationship, but it can only have one child - so seems to me to be a one to one relationship or an attribute!! When I design the relationship diagram and join the fields Key Topic to Key Topic - FM draws this as a many to many relationship, which seems wrong (Technique 1) So I redesigned the database using a join table (Technique 2) - This also seems wrong because one question can only have one Key Topic Line Item and not many. Paradoxically, both techniques seem to work in practice. I am worried if I use this technique I might end up in trouble further down the line. Any advice / clarification? Many thanks Garth Value List technique 1.fmp12 Value List technique 2.fmp12
  5. Hmmm - interesting - kinda makes me think there could be a way............
  6. Thanks for your input everyone - I now understand that I cannot do what I want using "simple" relationship techniques and need to use a script.
  7. Thanks Webko I had tried this technique and it is not working correctly for me. Whilst I can create an occupation in the portal window this does not transfer to the occupation table. Also in the Employment table this creates a fkOccupationID that is the name of the occupation rather than the serial number represent a new record. When I look at your screen shot you have an option ticked that is not available to me, "over ride data formatting with value list" - could this be the difference? I have attached the file again set up as you suggested and a screen shot of my window to show the settings Garth OccupationEmploymentTest file.fmp12
  8. Hi - I have tried to do this before and although I was give a script that did what I wanted (which I could not really understand!) I still wonder if my problem can be solved using FileMaker features without scripting. I have three tables People--<Employment>--Occupation In other words I want to record a person's job history. I have set up Employment as a join table, with allow creation of records in this table checked. I have made a portal to record the employment history and this seems to work; populating an employment field in the portal via the Occupation foreign key using a value list based on the Occupation Name from the Occupation table. What I would like to do - but don't know if it possible (and/or sensible), is use a simple technique to create a new record (occupation) via the portal in the occupation table, if the occupation does not exist in the current value list based on the current Occupation table I know I could do something similar using a simple value list, but I understand that if I base the value list on a table, this will have benefits if I need to change something in the future, say all cab drivers have to be rebranded as taxi drivers! Similarly, I could go to the occupation table and add a new occupation there. However, it seems more elegant to create the new occupation via the portal if this is possible. I hope that makes sense I have attached the database - hopefully that will help. Thanks for any guidance Garth OccupationEmploymentTest file.fmp12
  9. Result! Thanks - I had done this the other way round; I created a new TO for the QuestionOriginal and attached this to the QuestionsDerived. I don't understand why this does not work, is this because I am trying to create records from the perspective of QuestionOriginal, so any Portals have to have relationships created attached to the original parent table? I hope that makes sense!
  10. Help please! I am trying to write a solution to help manage the rewrite of an examination question bank. I am going around in circles trying to get one of the portals to work. Each original question can have multiple derived questions created from it; thus I have a table: QuestionOriginal and a table: QuestionDerived. I am trying to show the derived questions in the original question form via a Portal. I have set a one to many relationship: QuestionOriginal -< QuestionDerived and set the relationship to allow creation of records in the QuestionDerived form However, when I try and create a New Record by clicking in a field in the Portal (ContentTest) - I just cannot enter it to enter data to drive the creation of a new record. Any advice gratefully received. File attached. Thanks Garth Section one rewrite.fmp12
  11. Thanks - of course, I am aware of patient confidentiality. My database when it is finished will be held locally, for my personal use, to enable me to look at my outcomes. When it is complete there will be no demographics - just random reference numbers and the solution will be encrypted too. I have included demographics in the design as I have based the structure on the commonly used examples of customers and orders - it makes it easier for me to follow the tutorials. I understand some lines of code and see what it is doing, but some I don't, a long-hand explanation would have been helpful. I am a surgeon and there my expertise lies; I learnt my profession from experts and now pass on my knowledge to others. I am trying to learn filemaker from the ground up and I appreciate the experts here who share their knowledge and teach me.
  12. Hi Don thank you, thank you, thank you ....... That is brilliant. I have worked through the script (admittedly in a copy and paste fashion) and it works with my own database fields and tables. I would never have got there on my own. Would you be able to go through the script and explain what each line does? I would love to understand this some more. Is there a good learning source where I can find out more about how these scripts are written - I have used Lynda.com to get some understanding of Filemaker. Thanks again Garth
  13. Hi again. I seem to be going around in circles at the moment. I think i have set things up as you have. In the portal I have used the fkOccupationID, which is based on a value list based on the pkOccupationID and the OccupationName, from the Occupation table, but I have set this to only show the value from the second field, i.e. the OccupationName. This seems to create the correct entries in the Employment join table, when I use one of the occupations that is already in the occupation table. The problem remains that if I use the option to create other values - it puts the new occupation name in the join table; where a foreign key should be. What I would like to do, if possible, is create a new record in the Occupation table, that will then be available in future popup menus. I have had a look at the link you sent. I like the concept, but with a relatively long list of occupations, I think these will not be very practicable. cheers Garth People and Occupation v.3.fmp12
  14. Thanks Bruce - I had got myself in a muddle! I think I now have set things up properly, but I still cannot create a new record in the occupations table. If I try and use a popup menu with the option to created other values checked it creates a text entry in the join table in the _fkOperationID field, which is obviously incorrect. Where do I go from here? I have attached the latest version with this error included. People and Occupation v.2.fmp12
  15. Hi - I hope someone can point me in the right direction. I am trying to create a simple database (to help me understand a principle) before using the concept in a more complex solution I am trying to design I have three tables People--<Employment>--Occupation In other words I want to record a person's job history. I have set up Employment as a join table, with allow creation of records in this table checked. I have made a portal to record the employment history and this seems to work; populating an employment field in the portal via the Occupation foreign key using a value list based on the Occupation Name from the Occupation table. This also seems to work. What I would like to do - but don't know if it possible (and/or sensible) is use the "allow entry of other values option" in the popup menu AND use this choice to create a new record (occupation) in the occupation table, if the occupation does not exist. I know I could do something similar using a simple value list, but I understand that if I base the value list on a table, this will have benefits if I need to change something in the future, say all cab drivers have to be rebranded as taxi drivers! Or something like that. I hope that makes sense I have attached the database - hopefully that will help. Thanks for any guidance Garth People and Occupation.fmp12
×
×
  • Create New...

Important Information

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