Developer 2.1 problem/question

We are trying to create an application using Developer 2.1 and are having the following problem.

The first block runs a query producing a listing of all the master records. Users can narrow the executing a query to get specific records, like all records with a last name of Smith and the first name starting with T. This listing contains a few key pieces of data, but does not allow inserts, updates or deletions. To insert, update or delete a record, the user has to choose(click on) the specific record to be worked on. The double click performs a go_block to the second block, pulling up the specific record with all of its data. To get this to work we set up a relationship with block one being the master and block two being the detail, joined by the key. The way we set up the master/detail relationship for the same table may be causing our problem.

The problem is that when users add or edit a record and then save the changes, they are returned to the first record in the query from the first block. This is because to show the changes just made, we have to return to the first block, requery the master records and return to the second block with the changes. We would like the users to be returned to the record they are working on.

We did get around this problem when working with the full query list in block one - by setting a global variable "cur_rec" equal to the :system.cursor_record. When we make changes, save, and return to block one to requery we do a go_record(:global.cur_rec). This takes us to block 2 for that same record. However, if the users do an execute query and narrow the listing, the user always returns to the record with the same :system.cursor_record, but of the full query, not the narrowed query.

It seems that there should be an easy way to always return the user to the record they just processed. Any suggestions would be greatly appreciated.

Thanks
Ken Ballard (tcballk_at_monitor.tc.cc.va.us) Received on Wed May 24 2000 - 15:56:04 CDT