Sorry, Richard, cancel that last post! Having thought about it a bit more carefully:
assuming you have a 19 row portal with no scroll bar then the formula you need for the portal filter is: <newTO>::danSeq >= GetNthRecord (dance::danSeq ; Max ( 1 ; Get ( RecordNumber ) - 9 ) ) and the current foundset must be sorted by DanSeq ascending (or unsorted assuming danSeq is an auto-entered serial number) cheers Tom On 22 Jan 2011, at 14:31, Tom Elliott wrote: > Richard > > I should have said: > > You should only use the filtered portal method if EITHER the current foundset > is guaranteed to be un-sorted OR you can set the sort order for the new TO in > the new relationship's setup to be the same as the current foundset's sort > order (if the user has free rein for sorting then this not possible) > > cheers > > Tom > > > On 22 Jan 2011, at 11:02, Tom Elliott wrote: > >> Richard >> >> Solution Part the 1st: >> >> As Mike has said: build a milti-value key using GetNthRecord() >> >> OR >> >> create a self-join Cartesian relationship: >> >> <layoutTO>::<anyField> x <newTO>::<anyField> >> >> base your portal on the new TO and filter the portal with the formula: >> >> <newTO>::danSeq > Get ( RecordNumber ) - 10 >> and >> <newTO>::danSeq < Get ( RecordNumber ) + 10 >> >> (if you have, or will ever have, a vast number of records screen updating >> may prove to me unacceptably slow) >> >> >> Solution Part the 2nd: >> >> I'm assuming that you already have an invisible button in the portal; make >> sure it's behind everything else in the portal and Conditionally Format its >> fill colour with the formula: >> >> <layoutTO::danSeq = <portalTO>::danSeq >> >> If you haven't already got a button, you could use a text box containing a >> single space - or if you have a single field in the portal, you could >> Conditionally Format that. >> >> [it appears that you are attempting to use a calculated field to provide the >> highlight rather than native Conditional Formatting] >> >> >> cheers >> >> Tom >
