Stuck Again

[Totes]

I don’t know if I'm just fried from trying to figure this out or if I just cant get it.

I have a table called Case_Management (w/ __KP_Case_Management_ID) in this table I have a field called Case Number.

What I cant seem to do is have a new window pop up which will contain a large text field for the officers to type in and keep the case nuber from the main table when a new record is created (I have tried putting it in a related table, as well as in the parent table etc.) I also have the Case Number field also on this layout.

On the new window I have a button for a new record, when clicked I want it to create a new record with a blank text field(but still be related to the same case number).

For the life of me I cant seem to make this work…I have tried parent-child etc. ect. But I cant seem to get the “New Record” button to keep the current Case Number (relationship).

Here is a screenshot:

Click Here

The main table is on the left (1) as you can see the Case Number field.

The new window is on the right (2) with the case number field from (1).

The “New Record” button is above the Case Number field on the new window, when I press it I want it to create a new record so the officer can enter new information in the text box, but I want it to keep the Case Number from the main table.

Do I need a new table for the Case Summary Field (big text box)? If so what key do I connect the two together (I have tried combinations, but cant get the results I need).

Point me in the right direction please.

I thank you and my cat Schmukey thanks you.

James

Edited January 11, 2008 by Guest

[bcooney]

What's the difference btw your Case Number field and your __kP_Case_ManagementID field?

Sounds like you're looking to create children records for each Case. You'll need another table for these "summary" note records, perhaps "CaseNotes?" Each record in the child will have its parent _kF_Case_Mgmt_ID.

Will looking at this demo file help?

[Totes]

Hi,

Sorry I dont think I explained it well...the KP is just my primary key in the table (I put it on the post so that someone my be able to tell me a related table key to link it to just to let them know that I had a parent table with a primary key). I did try creating a child and link every combination of primary and foregin key combos I could come up with, all with no luck...anyway

The case number is just a regular field that the officer enters a case number in.

the case number field is the one I want to stay the same on the new window when the new record button is pressed and the officer is presented with a new blank text box to type in, the case number will still show in the new window no matter how many new records he creates (which of course is just a new blank text field to type in).

Sorry for the confusion.

J

Edited January 10, 2008 by Guest

[Totes]

First of all I apologize for such a noobie problem.

I have posted this here in the layout section…but it may be more of a relationship problem?

I have attached a copy of my db. (the user is admin / there is no password)

Here are the steps for my users:

1. The db opens to the Case Management layout, the user creates a case number a date etc. etc. (no problems with this step)

2. The user then presses the Investigators Summary button to open up the window so they can type text into. (no problems with this step)

What I cant make happen is this:

The popup window should only be related to the Case Number in the Case Management window….if a new record is created in the popup Summary Window it should still be related to the case number showing in the Case Management window in the background.

So in a nutshell, the officer opens the db, creates a case number (lets say 1234), then opens the Summary Window (which I want to only be related to the Case Case Management “Case Number: 1234) in the main layout.

Now if the officer comes in tomorrow and needs to add a new summary to a case number 1234 ….I want them to open the db and find the needed “Case Number: 1234” and then open the “Summary Window” and create a new record that will still be only related to that case number:1234.

Now there will be two summary records related to Case Number :1234

I have tried all types of PK to FK and FK to PK and I cant make anything go.

Hopefully someone can point me in the correct direction.

Thanks,

James

Case.zip

Edited January 11, 2008 by Guest

[comment]

See if the attached helps.

Some notes:

1. A one-to-many relationship should be based on the parent's primary key;

2. Your summary layout needs to be based on the summaries table;

3. Make sure you have a reason for every script step (actually, for anything else as well).

Investigators2.fp7.zip

[Totes]

Very very Informative!

I got it...the book I was attempting to use as a guide kind of had me going off in the wrong direction.

Thanks again, I have spent two solid days attempting everything I could think of or find in my books.

I can go to sleep now.

Hopefully Comment, I can get you out of a ticket one day or buy you a doughnut or something

James

[Totes]

Commnet,

One last question and Ill go to sleep.

The bar that is over the portal

with the :creationdate ::usercreate

What is that, and where did it come from, I thought is was just a button overlay, but I cant seem to dupliciate it.

J

[comment]

It's just three fields defined as a button (together, as a group).

You can go to sleep, but I can't get the vision of a doughnut out of my mind...

[LaRetta]

Hi James,

There is something else I saw which you might want to know. It bothers most people when they click into any field and ALL the fields produce that dumb dotted line around the fields. If you wish to eliminate that, go to Layouts > Layout Setup and uncheck, 'Show Field Frames...'

I wish FileMaker would make that the default. We must uncheck it EVERY time and it annoys me. wink2:

LaRetta

[Totes]

Another tip to go in my notebook....

Thanks folks!!!