Well, no doubt several ways.
uiName.switchindex("index_name")
for starters. uiName being the name of the child tableframe/object.
'index_name' being the name of the index.
So, if the field name you wish to limit the view of the child was 'machine', you might then
uiName.setrange(masterobjectName."fieldname",masterobjectName."fieldname")
This should place the child table in a restricted view, based on the index name, and with the restriction being the data in the 'fieldname' of the current record of 'masterobjectName' (tableframe?).
I did this with a zip code, phone, city set of tables. Depending on the field being used to 'search', all tables were switchindex()ed to the appropriate index and then limited with each character typed into the active 'search' field.
This allows 100% flexibility, with the same or better speed Paradox uses when tables are linked.
But there were no linked tables. Just several secondary indexes on each table. And each record in the table had a MEANINGLESS integer index; everything was done with secondary indexes.
Tony McGuire
"It's not about having enough time; we have the rest of our lives. It's about priorities.