I have a multi platform, multi user database system which is menu driven...

it has a file for phone messages, timesheets, purchase sheets, calendar, etc.

the employees now want me to devise a back button so no matter where they are, they can press back and go back tot he layout they had just come from...

The problem is that there are about 15 files with relationships....and I don't know where to begin to create a back button...

thanks

gary

If you have the Scriptology CD, there are some scripts to keep track of where you are including switching files. If you don't have the CD, try www.databasepros.com. and search for Foward & Back buttons.

What I'd do (after checking out thoughs links) is the have a global field in every database that is set to which database the user came from, then using a script you can send them back to the right one after.

Check out the 'Jazz Stack' plugin at

http://www.jazzmedia.com.au/shareware.html

There is a go-back example provided for use on a single database file. First understand how the example works. Then modify the example so that rather than saving (pushing) just a record ID each time, you save (push) a combination like "dbname recordID". On retrieval (pop) you can separate both items using the 'Left Words' script step, and go to the correct dbname and then recordID.

John

I have a back button that only is able to go back to the last layout. Is there a way to do multiple backs? mb

Try This example.

Download the attachment.

Great for Multi User or single user with a Single interface Solutions.

The way it works. When you click a nav button. It sets a global with the current layout Number. As you go the global keep track of the layout number you been to. With the last layout at the top. I use a calc field to grab the top number. The back button uses the go to layout by field, I use the calc field. Then it deletes the top number form the History field.

Thank you Todd, this is an interesting approach.

FWIW, I noticed that Layout seemed to be stuck on one layout name. I went into Define Fields and set the calculation to Unstored, and the Layout field then displayed Layout6 or Layout3, etc. as appropriate.

And then I noticed that the global "history" is not to cleared when the application is quit, so anyone using this may want to include a script to be performed on opening:

Clear [select, "history"]

So that a previous history is not present which might confuse a client at opening.

i have run into thois before when setting up a diary database and moving at a time.

set up a script made up of as many 'last records' as you require then attach that to your button

Check this tip file:

Mac

http://www.buliga.it/TipFiles/Navigation.sit

PC

http://www.buliga.it/TipFiles/Navigation.zip