Showing linked fields in a browse?

[jjfcpa]

I have a primary table and multiple secondary tables that are all linked to the primary table via a primary key.

I created a set with the primary table linked to each of the secondary tables in a one to many relationship based on the primary key of the primary table.

I created a form and put the fields from the primary table on it.

The secondary tables are on a tabbed object with each table in a browse object. There are as many tabs as there are secondary tables. I need to restrict the records displayed in the browses to those that are linked to the primary table via the primary key.

The browsed data will be for display only. I will be adding separate forms to add or edit records to the secondary tables via buttons on each of the tabbed pages.

Question 1.

How do I link the browses so that they only show the data linked to the primary key of the primary table?

Code examples would be greatly appreciated.

[Stan Mathews]

Re: Showing linked fields in a browse?

Unless I am misunderstanding, the records in the browses of the child tables are by definition only those records linked to the current parent table record. No coding is necessary.

Take a look at the default form for the set. Your form won't behave any differently in displaying records no matter how you set up the view.

[jjfcpa]

Re: Showing linked fields in a browse?

Thank you Stan. I was under the impression that I would still need to filter the records so that only the records linked to the primary table would be displayed?

Next question.

I now want to create a separate form for each of the browses created in the tabbed object for adding or editing records in the secondary tables.

I've created a set of buttons on each of the tabbed pages for "New", "Edit", and "Delete". Will I need to create a new set when I create the form for adding or editing records?

[Stan Mathews]

Re: Showing linked fields in a browse?

I was under the impression that I would still need to filter the records so that only the records linked to the primary table would be displayed?

No.

I've created a set of buttons on each of the tabbed pages for "New", "Edit", and "Delete". Will I need to create a new set when I create the form for adding or editing records?

That depends on what these buttons do.

If they create a new record in the pertinent child table, allow editing of the current record in the pertinent child table, and delete the current record in the pertinent child table, it shouldn't matter how you are viewing the record (form or browse). The only thing that should matter is how you specify the record to be actioned.

[jjfcpa]

Re: Showing linked fields in a browse?

No.

That depends on what these buttons do.

If they create a new record in the pertinent child table, allow editing of the current record in the pertinent child table, and delete the current record in the pertinent child table, it shouldn't matter how you are viewing the record (form or browse). The only thing that should matter is how you specify the record to be actioned.

Stan

One thing I need to do is populate the new child record with the primary key of the primary table. Not exactly sure how to do that.

So, I can just use the same set that I used for this form to create my new form to add new child records?

[Stan Mathews]

Re: Showing linked fields in a browse?

Tom Cone "wrote the book" when it comes to passing values between forms, which is what you need to do.

Check the attachment in this thread.

[Keith Hubert]

Re: Showing linked fields in a browse?

Since Tom wrote the book, like all things, someone has built a better mouse trap. In this case, it was the guys at Alpha.

Here is the code that Tim Kiebert fished out from What's New in V8. Yes, it has been there all this time.

dim linkdef as c
linkdef = "Link_field_in_child_table ="+s_quote(Link_field_[B]Object_Name[/B]_on_form.value)
dim p as p
p=form.ViewLinked("Name_of_form_to_opened_goes_here",linkdef,"Filter_would_go_here","Record_order_would_go_here","How_form_is_opened_would_go_here_eg. dialog_newrecord")
P.close()

There are a number of other options that can be used in this function too. See form.Viewlinked() in the Interactive Window.

Note: To make this script work, the link field from each table must be on each form, but can be hidden.

When the child form closes, the P.Close() helps complete the interaction between the two tables and the browse on the parent form gets refreshed.

Like all code, it may take a few goes to understand how it works and to get it right.

[jjfcpa]

Re: Showing linked fields in a browse?

Stan & Keith

Thanks for your assistance. I will be busy with this today and will report back.

[jjfcpa]

Re: Showing linked fields in a browse?

Tom Cone "wrote the book" when it comes to passing values between forms, which is what you need to do.

Check the attachment in this thread.

Stan

FYI - I downloaded the sample database in this thread and offer the following comments:

The samples are very old. I think this code goes back to 2003. There are some inconsistencies in the presentation - on the one table data entry, he provides forms to save or cancel the changes and on the example with a child table, you have to use keyboard commands to save or cancel changes. Worse yet, the ESC key (cancel changes) does not appear to work. In fact, I had to use task manager to get out of the example because I could not close the form at all.

If Tom has a more current example, I'd sure like to see it, but I don't think the examples in the zip file will do anyone any good till some bugs are fixed.

[jjfcpa]

Re: Showing linked fields in a browse?

Since Tom wrote the book, like all things, someone has built a better mouse trap. In this case, it was the guys at Alpha.

Here is the code that Tim Kiebert fished out from What's New in V8. Yes, it has been there all this time.

dim linkdef as c
linkdef = "Link_field_in_child_table ="+s_quote(Link_field_[B]Object_Name[/B]_on_form.value)
dim p as p
p=form.ViewLinked("Name_of_form_to_opened_goes_here",linkdef,"Filter_would_go_here","Record_order_would_go_here","How_form_is_opened_would_go_here_eg. dialog_newrecord")
P.close()

There are a number of other options that can be used in this function too. See form.Viewlinked() in the Interactive Window.

Note: To make this script work, the link field from each table must be on each form, but can be hidden.

When the child form closes, the P.Close() helps complete the interaction between the two tables and the browse on the parent form gets refreshed.

Like all code, it may take a few goes to understand how it works and to get it right.

Very strange because the form.viewlinked() function is not even listed in the help file, but using it in a code editor provides the parameters for it.

[Keith Hubert]

Re: Showing linked fields in a browse?

Hi John,

Very strange because the form.viewlinked() function is not even listed in the help file

That I'm afraid is one of the mysteries of Alpha and the value of this forum.

[Tom Cone Jr]

Re: Showing linked fields in a browse?

Ouch!

John, I'm sorry you had trouble with the "Basic Data Entry" example I put together 7 years ago for vers 5 users. Since then Alpha has changed how a "canceled" CanExit event for a form can be "uncanceled". The result is that the code ran fine in vers 5 but now prevents forms from being closed. When time permits I'll rework things.

In the meantime I suggest you take a look at a different thread that illustrates three different ways to pass field values from one form to another.

http://msgboard.alphasoftware.com/al...ht=Pass+values

Begin with form "Menu_main".

[jjfcpa]

Re: Showing linked fields in a browse?

Ouch!

John, I'm sorry you had trouble with the "Basic Data Entry" example I put together 7 years ago for vers 5 users. Since then Alpha has changed how a "canceled" CanExit event for a form can be "uncanceled". The result is that the code ran fine in vers 5 but now prevents forms from being closed. When time permits I'll rework things.

In the meantime I suggest you take a look at a different thread that illustrates three different ways to pass field values from one form to another.

http://msgboard.alphasoftware.com/al...ht=Pass+values

Begin with form "Menu_main".

Tom

I kind of thought the problem might be the way Alpha V10 is responding to the coding done in Version 5.

I sincerely hope you didn't think I was being critical of your code... I wasn't. It's just that it's hard to learn from code that doesn't work.

Thank you so much for the link and i will thoroughly investigate it.

[jjfcpa]

Re: Showing linked fields in a browse?

Tom

Just a quick reply to let you know that the example (Passing Values) is EXACTLY what I was looking for. This is the kind of information that newbie's like me are craving for. I can't thank you enough.