My client, a school bus company has a 9300 record student "Riderlist" database complete with student name, address, parent, school, etc, (provided by the school administration).  It is a simple, one screen layout.  There is a unique student ID number field and element for each student in the database.

The company uses the student ID number as a search argument to find each student's "page," and then assigns the bus number for that student, and files the record to call up another student record by ID number, and assign bus number, etc.

This is quite rapid in Q&A, since they use a search, then F10, then F7 to create the next search.
In Sesame, when in a search, a "Result set" of one is returned.  To search for the next student, it seems necessary to exit search and begin a new search.

Is there a way I have not discovered to file a student record, and immediately open a new search, with a new unique record called by a new student number?

I was able to point to the "Student ID" element with throwfocus (or even goto) but the problem is the search result set of one, saving, and then re-opening a new search routine for another uniquely numbered result set.

I hope there is an easier way to perform this rapid, record, by record, search and update.

...or am I missing something I should have seen in the book?

Thanks,
Jack

Now, why didn't I try that??  (Must have been another "Senior moment")

Erica, thanks a bunch!!  I am always amazed at the speed with which you provide help. 

(I am still waiting from an answer from MicroSoft on a question I submitted several days ago.)

Jack

You're welcome. 

The upcoming version also has a new way to do this using NotifyForm, which can prevent a Form from advancing past the last existing record.  It's less severe than forcing the Result Set position.

BTW, if you need to do this, get in the habit of checking @IsNew instead of testing for a blank value. If someone goes back later and blanks out the value you're checking, they will never be able to get back to that record again!

Just as a side note,  you should be careful when preventing forms from advancing to the blank record. It is usually okay on a top level form, but since it is the only way you can add a subrecord, you can prevent adding any records if you apply this technique to a subform.

In general, a slightly different programming style than you used in Q&A and good use of state programming can usually make it unnecessary to prevent advancing to the new record, making the whole thing a non-issue.

Quote:


It has been my experience that Erika, Mark, Ray and probably many of the other Lantica team members (the behind the scenes people) not only work 7 days a week they work 24 hours a day. It is amazing to me the level of support and care they offer to us users. I can only hope that the Shareholders of Lantica realize the value they bring to Sesame and appreciate them as much as we do.

  I hope we get to meet some more of the Lantica team at the conference (Ray without his reaper mask for one),  It would be a pleasure to buy him and the others a drink.

To quote John Kerry,
who was quoting George Bush,
who probalby never saw the movie.....

"BRING IT ON!"