This is mostly an English message board. I dont know if a lot of people here speak German.
Maybe you can see of there is a German Filemaker Forum. Or try to ask your question in English here.
I'm working with FileMaker 12 Pro (MacBook) and I'm looking for a way use a preexisting and unique patient ID in FileMaker. I have to be able to import several different excel sheets consecutively (each excel sheet contains a column with the patient's ID number). I should end up with one big spreadsheet containing all information about this specific patient. I will also have to import other of data and be able to update the database in regular intervals. I need a way to keep the unique patient ID to identify the patient and keep the dataset sorted. I tried to create 2 tables (first table containing a pk, name, ID number and DOB, 2. table fk, ID (as reference value from the first table) and the rest of the patient's values. unfortunately this doesn't seem to work out... I'm an absolute beginner with FileMaker - but maybe someone has a solution? Thanks
You will have to be a little bit more specific on what it is exactly that is not working out.
If you have an existing PatientId then you can use that as your Primary ID. You can import records in two tables.
I would guess you need a "Patient" table and a "Values" table.
In the Patients table you don't want the patient multiple times so you have to import using the PatientId as a Match field. So that patient information is updated but not added multiple times.
And then you need to check the box that also imports new patients that don't exist in the table yet.
If you import you data in the other table and relate it to the Patients table using the Patient ID then there shouldn't be a problem.
But I don't know exactly where it's going wrong with you.
My guess is that you using the Id serial number in the Patient table is not working out for you.
So use the Patient ID in stead.
Die Primaerschluessel muessen eindeutig sein - du kannst die bestehenden IDs nutzen (sofern diese eindeutig sind) und dann weitere Daten darauf aufbauen (zB Seriennummer in den Felddefinitionen, die anschliesst an die eingelesenen IDs..)
-> die eingelesenen Id werden dann zum pk (==ID)
Sollte problemlos sein, wie Guy schreibt
Ich kann in diesem Forum pro Tag genau ein posting schreiben - gibt heute also keine weiteren Antworten von mir. Dabei ist es egal, ob du im De-Teil des Forums schreibst oder hier - ab dem 2. posting muss ein captcha eingegeben werden, was unter iPads nicht funktioniert...
Allenfalls ist ein posting im Forum des FileMaker Magazins sinnvoll - das funktioniert wenigstens und wird nicht dauernd mit spams zugemuellt...
That's exactly what I've been looking for...
I'm not sure what I'm doing wrong. I deleted the Id serial number field, but if I use the existing patientID instead in the "patient" table and relate it to same patientID (Field with Reference to the patientID from the "patient" table) in the "values" table it doesn't work out... Do I have to relate it to a foreign key (serial Id number) of the "values" table instead?
In terms of importing new datasets: I guess, I would use the PatientID as a Match Field for both tables? Thank you so much for your help!
What exactly is it that "Doesn't work out" ?
You need to be more specific. I can't see what you are doing or what's going wrong.
If you don't give me any information then I can't even begin to guess what the problem might be.
The relationship needs to be between two fields that could possibly contain the exact same value.
So in your Values table you take the PatientID number. And in the Patients table you take the PatientsID number.
Make sure they are the same type of field. Like number or text.
Then you should be able to create a portal on the patients layout to display records from the Values table.
For your import you need to think about what you want. If you import into the Patients table you want to use a match field so as not to import patients that already exist. So there you would need to use a match field.
But I don't know what the other data is. If it's always new data then you don't have to use a match field to import into the Values table. You just import everything.
If you sometimes have duplicate Values records then you need to find a way to uniquely identify these values records and use that as a match field.