in pre-separation versions, i had some calculated nav-icons for go-to-last/prev/next'etc. record. they took their images from source fields, depending on where you were. for example, if you're on the first record, the go to first record button appeared dimmed.

with separation, this is not so easy, because the buttons and images now should belong in the interface file, but the logic which button to display is dependent on the data file whose table happens to be displayed on the interface layout.

is there an easy way to know in the interface file which record of the target table is active? hope i made myself clear.

This shouldnt really be an issue. If a layout is created in the UI file that displays the info reflecting a TO of a table in the DATA file, then it should work as if it was local.

What is your calc logic for displaying the different buttons?

hmm.. you're right it does work perfectly. but if i do that, graphic interface items are pulled from the data file, because only the data file 'knows' which record is currently viewed.

i thought that such graphic images should be in the interface file only. but how does the interface file know which record i'm navigating?

It should. There are a few different ways to go about this.

1. If you have a fully locked down navigation where everything is scripted, then you could tie setting some globals with your navigation scripting. However, if one performs a manual find then it will not work. If the find is scripted, then it could work.

2. You could reference the UI global images in your data calc.

3. You can use relationships based off your data.

I have attached a sample file that displays all 3 methods.

Seperation_Navigation.zip

john,

this is way more than i could have asked for. thanks a bunch for the template! i think i'll go with the scripted method, but it's great to also see the alternate way of doing things.