I still must be missing something in my understanding of Sesame and Natural (automatic) links. So I am hoping if I post what I think is the case someone can explain were my thought process has gone wrong.  In Sesame:

An application contains databases
A database contains forms
Forms contain elements

Data can be displayed on more then 1 form by having elements bound to the same underlying field.

A database can be on multiple forms by way of subforms.

So lets say I have  2 databases in my application 1 is The community and 2 is The Block.

The database called The Block has a form called myneighbors that has an element called neighbors.

The database The Community has a couple of text elements and 2 subforms (on a tab of course) 1 is a table view subform of the form myneighbors from The block database one is a form subform of the form myneighbors from The block database.

If the subforms are set up as natural (automatic) when I go into The community database and enter data into its elements and then enter data into the form subform it links that data to the parent record (automaticaly) then I can save and exit.

When I later go into the community database and search for the parent record the data that was entered into the form subform appears.

If I go into the community database and search for the parent record the data that was entered into the form subform should also appear in the Tableview Subform since the tableview subform is the same bound elements that are naturally linked to the parent  (just displayed in tableview rather then form view) Sesame should display the child data.

Since this is not what happens were have I misunderstood this. 

Thanks

I believed I was choosing show existing Natural Childrecords (name) On the second subform  but when I just went to look at a couple of my subforms settings box 3 is blank. (I would swear I chose show existing Natural Childrecords (name))

I will re create the subform being very cognizant of my selection.

Thanks for the help.

Quote:



When I right click on my subforms and select subform settings the subrecord field names are the same. However box 3 is empty and I am 100 percent sure I selected show existing Natural Childrecords (name) this time. Is this box supposed to clear itself?

Thanks

The reason it does not seem to work as I thought is because even  though I am saving the record after I add data in the detail subform, until I re search on the record it does not show in the table view subform. I guess I was still thinking like a QA user. I am very used to being able to put data in an element/field in QAWIN and switching to other forms and seeing it immediately.

I guess I should start thinking of a button with a subroutine that takes the rec number and re searches when pressed.

When we put in that capability, I think we envisioned that you would use one or the other on any one parent form, or maybe switch between them using form visibility.

I am now looking into some way you can use just one subform and have it toggle its "view" back and forth via programming.

Wish me luck - I'm going in!

Mark, me and all of my imaginary friends are rooting for you!

You can do it!

We'll look for you on the other side.

Steve

By the way, your idea of hiding table view and showing form view when a user wants more details was very clever. Thanks for that little nugget!

Just wondering, when those imaginary people are not talking to you are they talking about you?

I think mine are 

Would it only complicate things more if we created additional subforms to 'drill down' to specifics on a record, rather than subforms.

For example, starting at the top:

Parent form: Continent, gives an average population by region, shows total number of coutries, cities, and counties and other info pertinent to a continent and has table view subform of Countries.

From here, a user can type a line number in a box and press a button (or just click on an item in the subform) to close parent form and open the below form automatically searching for the country that the user selected.

Subform on Continent form: Countries, shows pertinent info about the COUNTRY, and contains a subform called Cities.

Again, user can type a line number in a box and press a button to close parent form and open the below form automatically searching for the CITY that the user selected.

NEW FORM(and new database?) called Cities: shows pertinent city information and contains table view subform of Counties, or Neighborhoods, etc.

Again, user can type a line number in a box and press a button to close parent form and open the below form automatically searching for the County that the user selected.

Final form opens (new database?) showing details of the county that the user selected.

This 'drill down' technique could continue on and on depending on how specific the user wants to get.

The benefit here is that the user can start at the top and get a broad view of their data, seeing averages and totals of the specific info from the top. It is then easy to zero in as needed.

I beleive Bob_Scott is doing the same thing, but using tabs. Which method would be preferred? Certainly programming is easier with fewer databases involved.

Any thoughts?

Steve