RecordID versus Record Number with Go To Record

[cclub75]

I'm working on a "navigational" system, where user can "return" to where he came (with several tables, layouts etc). My idea was to store RecordID and LayoutNumber into 2 globals. And then use them if the user decides to "go back" from the previous record he saw. Anyway.

Am I missing something ? But looks like FM offers RecordID but do not allow to use it with a proper function.

The function Go To Record use RecordNumber (which is the number of the record whithin the found set, so it can change of course) :?

Do you know a way to use RecordID instead ?

[-Queue-]

Crate a relationship from the global to RecordID and use Go to Related Record [ ; relationship; using layout "your layout"]. Note that 'Show only related' is not selected, so that if the record is already in the layout's found set, it won't omit all others.

[OnTheOutside]

I'd like to do this too, but I'm not sure how. I have the same multiple table, multiple layouts thing going on. Imagine an Invoicing system where you are looking at a particular customer, then look up an Invoice and go back to the Customer screen and have to search for the customer you were just looking at.

It seems I could do a sub-script to get the current RecordID for each table and store them each in a global, then when someone went back to a layout they had previously been on then it would feed the global value as the record to go to for that table/layout. ...?

[-Queue-]

If you don't navigate to a different customer record when you look up an invoice and move to a different layout, then I don't see why you would need to search for the customer again when you return to the original layout. It should still be the currently selected record.

Perhaps you are talking more in general about a 'Back' button? If so, do a search for "back button" on this site.