Tagname Not found

[Thomas Holt]

Hello,

Hopefully the attached file will highlight my problem. I am trying to alter the way records are displayed in the browse of the "Client_History" form (based on child 'Rental' table, one-to-many link).
At the momemt I have a script firing no the forms OnActivate event. This produces a "Tagname not found" error message. I have tried numerous variations of this script trying to use either the "mov_id" index or the "datehire" index, all with no success.
Any help with this problem as always greatly appreciated.


Many Thanks
Cheers
Tom

[CALocklin]

RE: Tagname Not found

Tom,

First, for future benefit only, there are a couple basic errors in the script even though they don't really matter here because you can't set the index of a child table like you are trying to do (and many of us have tried before).

- Table.current(1) refers to the parent table.
- Your expression idx=tbl.index_primary_put(datehire) would need to be changed to idx=tbl.index_primary_put( "datehire" ) with the quotes around the name of the index.

The only way I know of to set the sort order of the browse is to define it in the set definition. In your case, the linking field definition for the child table would be:
Client_id + Rent_date

I quite certain this will still work correctly when creating new rental records and the Client_id will automatically be added to the child table but you might want to verify it. If not, you might need one set for data entry and another for viewing.

The one thing I'm sure of is that a set linked like this can't use referential integrity but you don't have it set up that way now so it doesn't matter.

[Thomas Holt]

RE: Tagname Not found

Hello Cal,

Many thanks for the time taken to respond to this question. You have cleared up a quite a few issues for me.


Cheers
Tom

[Steve Dentler]

RE: Tagname Not found

I've seen any number of postings that indicate A5 can not query the child records in a set. I've have no idea how this started, but you can, and as far as I know, you always could. Now you can't change the linking key, of course, but if you can apply a filter, you can apply a query.

I am attaching your DB where the set now opens with an abitrary query filtering out certain dated records (it's run from the OnInit Event). I have also placed a button on your form to re-query the records based on a user entered date. You'll have to navigate to the second record to use the query button (first parent record has no items under the initial query).

While this may not be all that useful in this situation, it's quite handy in others. For example my general ledger displays a field to let the user select which fiscal year detail postings to display from a drop down box. The OnChange event for this field re-queries the records and displays only the activity for that fiscal year.

Not to mention.....I hate filtering data; always seems like such a waste of a good program's time.

[Tom Cone Jr]

RE: Tagname Not found


Steve,

There are queries and there are queries. The language is not very precise sometimes. At the risk of muddying the water, I will plunge in head first:

Using a set based form it's definitely possible, as you describe, to limit the range of displayed child table records with a query. (show me all the child table transactions between january 1st and december 31 for calendar year 2001) But this does not affect the range of parent table records in the current 'view' of the set, just the range of child table records that are displayed.

What you cannot do in a set based form, is run a query against the child table to find and display only qualifying parent table records. Folks sometimes want to select parent table records based on criteria which are found in the child table. i.e. to show only those parent table records which happen to be linked to child table records that satisfy the query criteria. (show me only those parent table records which have linked transaction records falling in the range from January 1st to December 31st for calendar year 2001)

In some cases flattenquery() can be used to overcome this limitation. I often will elect to invert the set, instead.

Hope this clears things a bit...

-- tom

[Steve Dentler]

RE: Tagname Not found

What you cannot do in a set based form, is run a query against the child table to find and display only qualifying parent table records. Folks sometimes want to select parent table records based on criteria which are found in the child table. i.e. to show only those parent table records which happen to be linked to child table records that satisfy the query criteria. (show me only those parent table records which have linked transaction records falling in the range from January 1st to December 31st for calendar year 2001)
-------------------------------------
That's not what I've read over the past several weeks. I could probably pull up the threads but won't bother. There does seem to be some confusion on when you can run a query against just the child records within a set. But that's all old news....because now (Version Five) you can also run a query on child records to pull only the parent records in that you want (as you're probably aware from the release notes).