Hi all

to frame my problem

i have patients that may have varying numbers of medical procedures/histories.

I can easily make a portal from my main database table to a child table using the patient ID as the related field. This allow me to enter in the medical history for that patient using a portal rather than a repeating field. however to make this UI nice i would like to have one portal that is used to enter new records (histories) displaying only one row "ie the new one" and one portal below it that display the histories already entered for that patient (standard portal with scroll bar type look)

Any ideas how i would go about doing this?

Many kind regards

Ozziggy

From the top of my head: make a button "New entry" that would execute next script:

New Window

Go to layout: (here you chose the layout where you enter all the details)

When you finish with data entry click button "Done", for example, that would execute script: close window.

If you won't like it, let us know... Thanks.

Hi Paavo Thanks for your response Background: the main table is a case report form that list an adverse event. These are unique The related record in child and parent Is the unique case report identifier. Child table is a data base of medical histories(ie past procedures, ,like for example hip implant, and knee arthroscopy) The advantage of entering data through the last portal row is that it creates medical history record with the currently viewed and created unique cases identifies. The problem is entering data into the last portal row can seem confusing for the user. So what I was hopping to do was have one area that I can enter a new history and the other being a portal that that list all histories for that current case. Thanks for the new window suggestion. I have tried this but I end up creating records in the patient history table that are not linked to the case identifier from the main case report table....this is a problem. Cheers zig

See the attached sample.

 

The new entry portal is based on a new TO of procedures.  The portal is set to allow creation of new records.  A new procedure record has a field isNew that is automatically set to 1.  That field in Procedures2 is related to a field isTrue in patients which is always 1.  The Enter button sets the isNew field to 0, so there are no related records anymore in the new entry portal.

DataEntryPortal.fmp12.zip

Wow!

 

Thanks Doughemi ....This is exactly what i wanted to achieve. Now the challenge for me as a complete newbie, is to work out just how you did that from deconstructing / reconstructing your graciously provided example file. This could take some time, because even though i have a few bits of paper that claim that i am smart, i feel like i blundering idiot in filemaker terms!

 

I think without the kindness of others the new lambs like myself would surely be wolf bait.

 

cheers Zig