looking for a headache

[Corey Pennycuff]

I need some help in manipulating records, please. My situation is as follows:

I am constructing a program for a small institute. One of my form is built from a set containing the class information (name, teacher info, etc.) in one table, linked one-to-many to a table containing the book information (title, author, cost, etc., linked by an ID number) for the books used in that class. This way I have a set showing each class, as well all the books used for that class.

What I would like to do is that, when the form opens, a lookup table opens, allowing the user to select the class. Once this is done, the form should then display that class' information and it's book list in a browse. Also, when the lookup field changes to a different class, then that class' information and book list should appear.

What happens is this: The form opens showing the first class, and its information. This is fine. When you lookup a different class, however, the form does not show that class' record. Rather, it tries to replace the class' information with the new class' information.

In other words, in the set we have:

CLASS 1
Book A
Book B

CLASS 2
Book B
Book C

When the form is opened, the information for Class 1 is showing. After doing a table lookup (on the name or ID), you select Class 2, the set changes to:

Class 2
Book A
Book B

Class 2
Book B
Book C

What it is doing is superimposing the selected class' information over the old class' book list. This is wrong. What is needed is for the form to simply show the record that was selected in the lookup table.

Is this possible, or am I trying to do something Alpha Five was never intended to to?

Thank you for your time. Any help will be appreciated.

[Stan Mathews]

RE: looking for a headache

You need to "refresh" the data displayed on your form. The "child" data is not being superimposed, it's just not changing at all.

You can do this in one of two ways.

Edit the action for the "OnFetch" event for your form and enter the xbasic

this.resynch()

or you can name the fields from the child table and use

childfield1.refresh()
childfield2.refresh()

etc.

Hope I got this right. If I didn't you'll have other replies.

[Tom Cone Jr]

RE: looking for a headache

Corey, you probably don't want to use a field rule table lookup in this circumstance. The field rule table lookup is intended to help people doing rapid data entry work, to permit them to pick an entry off the lookup list and have it automatically be loaded into the fields in the current record on screen. Saves tons of typing and typos.

So, if I understand your goal correctly I'd advise you to disable the lookup rule on your class.

Then, when your form opens use one of the Find functions on the toolbar to find the correct class.

As I see it you are trying to quickly navigate to another record in your set, rather than add new class records, so the Find by (text, form or key) should work just peachy!

-- tom

[martinwcole]

RE: looking for a headache

also, if you put a small embedded browse on the form, using the parent (the class) and another small embedded browse on the form using the child (the books), as you scroll throught the classes, the books for the classes will refresh on the second embedded browse automatically.