Moving dead residents!

[slugbut]

Hi,

Thanks for all your help so far.

Everything is working but the nurses have asked whether they can have a separate layout that shows all the dead residents!

I showed them the find function but they said they would like a layout that included the reason they left or deceased.

should I create a new table, create a relationship between the two and use a lookup?

any help would be gratefully received,

Thanks

[Cabinetman]

Hi,

Thanks for all your help so far.

Everything is working but the nurses have asked whether they can have a separate layout that shows all the dead residents!

I showed them the find function but they said they would like a layout that included the reason they left or deceased.

should I create a new table, create a relationship between the two and use a lookup?

any help would be gratefully received,

Thanks

I would think a layout with a portal would work based on a relationship.

Portals are me weakest (like I have a strong) area so hopefully you know or someone else will chime in on the best way to set the relationship.

Then just going to the layout will have the list of all matching deceased.....

[Aussie John]

Seems to me that you wouldn't have a parent child relationship but a sibling sibling one. In other works for each resident there would only be one 'passed on' patient. Not a very efficient usage of a relationship.

Why not just add an extra field to your main table "reason for leaving". I could understand why you might want to move these patients from the active table to a 'passed on' table but the parent child relationship wouldn't help here.

You could run a script to export/delete the deceased patients to a new table. This could be run as a script trigger on the entry to the relevant field.