"primary key field " is there any way that I need to set the field up to be the primary key field?

drastixnz wrote on Jun 19^th, 2007 at 7:21am:

Based on your previous post where you wrote "I have created a subform that is relationally linked and I used a common field which is record number", it sounds like you have already set it up. It's something that is done when you first create the subform in Designer. If you built it as a relational subform, you were required to specify the "Parent Record Field" in the Subform Settings dialogue box. You can view it now by opening the parent form in Designer, right-clicking on the subform and selecting "Subform Settings" from the mini popup menu.

Hello Carl,
I am sorry for the muck up, this is what I want.


I have a form called "Plan Track V0.2" within that form is a subform (Plan Tracking Log) which contains a table called "Plan Tracking Log".

I do enter the data into "Plan Tracking Log" via the Subform I enter it in at a different place, in the program.

When I open the form "Plan Track V0.2" I want the subfrom to show all of the data, that has been entered.

I am sorry for the misunderstading

Paul D

Carl Underwood quoted : Quote:


Paul hasn't coded for the restriction by months yet. He's working on just seeing the table filled up first, then will code for limiting whats seen

drastixnz wrote on Jun 19^th, 2007 at 9:17pm:


OK I believe you are saying you want every record to show from Plan Tracking Log in the subform no matter what record is showing in “Plan Track V0.2”

There is probably better and smarter ways to do this, I am sure the Lanticans or others will also chime in, but this should work for you.

Ad an element to Plan Tracking Log  named something like logKey.  Use logic to fill it with an X whenever a record is created. (one time mass updatate all existing records to have an X in this element)

Now

Ad an element to “Plan Track V0.2”    named PlanTracklogKey.  Use logic to fill it with an X whenever a record is created. (one time mass updatate all existing records to have an X in this element)

Open  “Plan Track V0.2”  and create a subform selecting Plan Tracking Log for the subform and select element PlanTracklogKey for parent record field and select logKey for child record field.

Now whenever you work with a record in “Plan Track V0.2” a match of the records will be found with every record in Plan Tracking Log and they will appear in your table view subform.

If you need any assistance in creating, updating or logic to fill the keys in the records let us know.

With Sesame there is always many ways to accomplish a task, this is just one method. I am not sure it’s a great method but until others chime in, it is an option.

To mass update existing records open the Plan Track V0.2”  Database in search / update mode with the command tree open. (Open the actual application not Sdesigner)

Press f7 f10 to select all the records

On the left hand side of screen on the bottom half of the command tree (I think it opens in default as sort) click the third arrow until it is on Mass update property.

click on PlanTracklogKey (or any element it really does not matter) to open the mass update editor.

Enter:  
PlanTracklogKey = “X”
Click on test to check logic
Exit editor

Click on the first down arrow and select run.
Select continue to have it all run or select interactive to do 1 at a time

Do the same thing for Plan Tracking log database using element log key.

This now set both key fields in all the records to be X

Your relational table subform will now work if it is set up correctly.

Now open Sdesigner to make all future record key elements  be x you will need to put logic like (example below) in both databases. (just switch PlanTracklogKey with log key)

If Not @isblank(your element name that proves you want to save this record goes here)

Then
     {
     PlanTracklogKey = “x”
     }


Hope this is somewhat clear. Let me know if I lost you somewhere.

Robert

Quote:


Just wanted to expand a little bit on what Carl said. Yes, Sesame does understand retrieve specs in the Parent key but the full family of retrieve spec options is not available to the Relational Link, i.e. functions like Min and Max will not work. The Relational Link does understand everything that is valid to put into a restriction spec. So if you just think of the Parent Key as a restriction spec as to what children it can display, you're gonna be on the right track. Restrictions are covered on pages 120-122 of the Sesame 1.1 User Guide in case anyone needs a reference.

-Ray