I've been utilising slides and pop-overs for data entry to try a minimise the number of layouts needed. Working lovely so far.

 

I have a 'Company' screen, that upon entering shows a 'view only'. It has buttons for 'Find', 'Edit' and 'New'. Clicking these reveals buttons pertinant to the button clicked.

 

When you cancel find mode, you go back to the record you were previously viewing. These seems to be default behaviour...fine.

When you cancel edit, you obviously go back to the record you were previously viewing...fine.

When you cancel new, you go to the last record in the table/found set...jarring for the user.

 

So, when cancelling the entry of a new record, how can you script to navigate back to the record you were viewing before you hit 'New'.

 

Hope that makes sense.

 

FM 13 PA | OSX 10.9

When you make the new record, save the Current RecordID(Primary Key) somewhere before making the new one...Maybe to a global variable ($$). When you hit cancel, Have the script delete the cancelled record and then to back to the previous layout and Script a Find for the previous record using the saved key from the first step.

 

Let us know how it works out.

When you make the new record, save the Current RecordID(Primary Key) somewhere before making the new one...Maybe to a global variable ($$). When you hit cancel, Have the script delete the cancelled record and then to back to the previous layout and Script a Find for the previous record using the saved key from the first step.

 

This will change the found set, which may not be desirable.

 

Since the found set doesn't change when creating and immediately deleting a new record, it will be less disruptive to capture the record number of the original record, then go back there.

This will change the found set, which may not be desirable.

 

Since the found set doesn't change when creating and immediately deleting a new record, it will be less disruptive to capture the record number of the original record, then go back there.

 

I like that solution. Probably faster as well.

I'm guessing then that there is a Get(RecordNumber) or similar script step. I'll have a look at putting that in a variable and see how I get on.

 

Thanks.

Perfect. Thanks both.