Hi,

I created a join table where records are stored via a script.

I would like to stop these records from being deleted when one erases a record in the "mother" table.

I tried the checkboxes in the TOG. Didn't work.

Does anybody have an idea how to do this?

If you disable the "Delete records in this table…" option, they won't be deleted. However, you need to make sure the option is disabled in ALL instances of the join table being connected to the "mother" table.

I tried this but it doesn't work as I'd like it.

I attached a sample in which I explain my goal.

perhaps I need a different approach.

Would you be so kind to have a look.

Question.fp7.zip

"Deleting this record will delete the record in the portal below"

No, it won't - the record (in PatientProcedures) is still there. But the field "procedure" in the portal below is coming from the parent record in Procedures. If you delete the parent Procedure, then it can no longer be shown in the portal below. Similarly, if you edit the parent Procedure, the change will be reflected in the portal below - because it's the SAME field.

I am afraid I have no idea what your file is supposed to do, so I cannot suggest an alternative.

I would like to prevent a record saved in patientprocedures from being changed or deleted.

E.g. a patient underwent a appendectomy. Later on for some reason I delete appendectomy from the list of procedures.

So the records save in patientprocedures can't display appendectomie anymore as this field is gone. Is there a way to prevent this.

The record in PatientProcedures can display "appendectomy" because it's related to the appendectomy record in Procedures. This is a good thing - it saves you the trouble of entering "appendectomy" every time someone has one, and it allows you to change "appendectomy" to "appendectomie" in one place and affect all related records.

OTOH, it also means that if you delete the appendectomy record in Procedures, the related records have nothing to display. The best way to prevent this is NOT to delete that record. Although you COULD lookup the procedure's name into a field in PatientProcedures (a lookup copies the data), I don't see why you would want to.