Button to display a related record

[Rehoboth]

Hi

I have created a drop down menu that displays the nae field for all records.

I want to create a button beside this field that when pressed will take the use to the record of the name selected above.

Any idea how to do this?

Thanks

Trevor

[Inky Phil]

Hi trevor

you do not necessarily need a button for this. Just create a global field and establish a relationship . I have prepared a down and dirty example for you.

Hope it helps

Phil

trevs_dem.fp7.zip

[Rehoboth]

Phil

Thanks for taking the trouble, really appreciate it.

Great idea. Only thing is in this situation I really want to be able to jump to the whole record as there is oodles of information that I need it to be able to access.

Trevor

[Inky Phil]

OK Trev, see if this does it for you.

Get back to me if you want to know how to improve it any - it is real basic.

Phil

trevs_dem.fp7.zip

[the_kid]

Hi Phil,

This is very close to what I'm trying to achieve. Is it possible to pull some of the data from another table? That is, have the drop down in a table called "log." When you choose Fred from the drop down, it would pull Fred's address from the "trevs_dem" table into the log table. Try as I might, I can't seem to figure this one out.

Thanks in advance,

Roger

[Inky Phil]

Hi Roger and welcome to the forums,

One would not normally physically pull the data from table b into table a. That would give you the same data in 2 places and all the problems that that might bring.

What you would normally do is link table a to table b by a relationship thereby allowing you to select a name in table a and display (share?) the related data from table b.

The attached dem does what I just said which is much the same as trevs dem but with 2 tables instead of one.

If you really do want to pull the data from the data file into the log file I can show you how to do it ( tommorrow am) but you really do want to think about it.

The only times you would normally transfer the data is when you want a snapshot of the data at that point and store the snapshot ( invoice details perhaps) but if you just want to see the guy's current details then a relationship is the way to go

Let me know

Phil

kids_dem.zip

Edited February 1, 2007 by Guest

[Rehoboth]

Hi Phil

Thanks for this. You have guessed I am very new to Fm and appreciate your help.

I don't quite understand this whole layout buisness yet. However, is there a way to stay in the one layout and just jump to the associated file?

Trevor

[Inky Phil]

Hi Trevor,

The short answer is no you cannot stay on one layout and jump to another file. What you can do though is stay on a layout and show data from another related file.

What you will find if you take a close look at the file attached to my first post is that the fields that are revealed are in fact related fields and I do not move from the layout.

The second sample file does almost exactly the same thing as far as the user is concerned but instead of showing fields on the original layout which are related it switches to a layout that shows data from a related file

Please forgive me if that sounds a bit more complicated than it needs to but it is important (for your sanity if nothing else) that you study those examples until you understand what is happening in both of them because as you progress with FM you will use both approaches depending on the circumstances.

Don't worry if it takes a little time to sink in - I remember the frustration only too well. trust me it is very rewarding when you do get it.

get back to me, in the meantime I hope I have helped

Phil

[Rehoboth]

Hi phil

Ok, I am getting the picture. If the user jumps to a different layout could it have all the same functionality so that the user doesn't need to know he is on a different layout. Can he input data etc? But oviously on the button in question, on the new layout it would jump back to the existing one?

Do have that right?

Thanks!

Trevor

[Inky Phil]

Absolutely trevor.

In Filemaker you prepare a different layout for almost anything that you want to do. My own current project has some 400 layouts.

Every layout does what YOU want it to do. A layout is your way of communicating with the user.

Have fun. Do not be afraid. Layouts are your friend!

Phil

[Rehoboth]

Hi Phil

in theory I get it, in practice I just can't get it to work! I suppose a little frustration is probably good for the soul!

Here is what I am doing:

(1) I have a field called "Discipled by" which has a drop down menu with values taken from "full name" (lists all the names in the database). This part works.

(2) Under - define relationships, I have pulled an arrow from "full name" to "Discipled by"

(3) In the button set up I have it set to got to "related record" and take the file from "pastoral database" and to display in "Found Full name" lay outs.

This seems to make sense in terms of the order of things but all it does is change to the "found full names" lay out but doesn't change the record information.

Any help appreciated.

Thanks

Trevor

[ovrdrvn]

Slightly similar problem: I'm using the Go To Related Record to find all the related records of the found set in my table "visits". I need to have a count of the "patients" displayed in my original table/layout which is the "visits"child table. I was told there was a way to do it with a variable field and then a global field in the report...but I can't understand this.

Anyone?

[LaRetta]

If, while in Visits, you need to count the unique Patients from the found set, then it (usually) means you have a PatientID in Visits? Since this is what the relationship is based upon, you can create a field (summary, number) with Count ( PatientID ). Then add a Grand Summary to your report and place this field in it. It will display the number of unique Patients from the current found set.

If I've missed understanding your need, please let me know and we can adjust ...

But what you describe would be something like (from your Patients table), script of:

Set Variable [ $CountPatients ; Get ( FoundCount ) ]

GTRR etc

Set Field [ global ; $CountPatients ]

But I question whether this is necessary because FM already knows this information.

LaRetta :wink2:

[comment]

you can create a field (summary, number) with Count ( PatientID ). Then add a Grand Summary to your report and place this field in it. It will display the number of unique Patients from the current found set.

I think it will display the count of all found visits that have something in the PatientID field - i.e. the count of all found records.