trouble with relationships

[john j]

I am trying to develope an office database which involves tabulating data from multiple layouts into text files. I have about 8 tables linked in a one to one fashion by a "patient number". I am trying to pull data through the link to populate multiple fields. I have exhausted filemaker pro advanced and "using filemaker 7" and basically have gotten nowhere. Getting frustrated. My links do not work and cannot pull data through. I have tried GTRR, tried using globals to store data and nothing works. The record numbers have to be unique and discontinuous (have to be entered manually) because of the chart system in the office. Also I have tried auto entering serial numbers and so far zip for working. Could you take a look at the file and point me in the right direction.

--------thanks.

johnj

ROS.fp7.zip

[bruceR]

Well one thing I see is that your "go to layout" steps don't do anything. They just say "go to original layout".

The second thing I see is that, although you have a field for patient number in all the related tables, you are not setting the patient number in any of the related tables so of course you have no related data. You have records for Patient RE000001 and RE000002 but none of your related tables have either of those values in Patient ID.

On the MEDS layout you are not displaying any actual fields from the MEDS table.

What do you mean by saying you are "pulling data through a relationship" ?

[john j]

What I am trying to do is to copy the patient number from the first table (patient registration) to the second table (ros) and then pull the patient's name, date of birth(dob) and other identifying data through the relationship by using the record number. I have tried to store the original patient number in a global and then use setfield to store it in the second(ros) table. I have tried lookup, copying it through a related table link----> patient registration::patient number, GTRR with and without new record request but it does not show up in the second table. The second field always remains blank. It seems to me that the second table should show the same value in the patient number field as the first table in a one to one relationship.

I guess that I am missing something in the concept or have a validation/auto enter/storage problem. If I could get PATIENT_REGISTRATION TO table to talk to ROS TO table, I think I could figure out how to make the other tables work.

thanks,

john

[Søren Dyhr]

The second field always remains blank. It seems to me that the second table should show the same value in the patient number field as the first table in a one to one relationship.

I allow myself to take it granted that you not are speaking of repeating fields??? Do you get a portal of the first record repeated several times??

If so is it one of tougher issues to grasp, especially when reading Danny Macks description in "Migration Foundations..." - However are we lucky that Matt Petrowsky have made an efford to explain it better:

http://previews.filemakermagazine.com/videos/541/GraphRules_full.mov

--sd

[Fenton]

In your script to create a new record in Ros, you are NOT setting the Patient ID into a global first. Nor are you adding it to the Script Parameter (an alternative method). You are not setting it into the Ros record. So it isn't there.

Set it into a global (in either table). Go to Ros. New Record. Set the Patient ID foreign key to the global. Commit.

Other fields which you want to "pull" data could be auto-enter, either Look Up or Calculation, using the relationship back to Patients. They do not need to be scripted. But nothing is going to work until the foreign Patient ID has the same value as the Patient ID in Patients. There is no relationship without that ID in both tables.

(P.S. Don't use "record number" for the name of your primary patient ID in Patients. Use either SerialID (generic) or PatientID (specific, the common method), with whatever prefixes you see fit (if any). "Record number" means the position of the current record in the Found Set.)

[john j]

That is exactly what I needed! Being a novice, I have spent hours trying to get the relationship to work but that was the key.

Again, thank you very much!!!