Stumped once again!

I think this should be simple.... I have about 3000 records and from a list view I want to be able to jump to an approximately close record.

Example:

I have a global field - Last Name Global.

Also a field - Last Name

I type Smith into Last Name Global in the header section and click on the button.

From whatever record it's on in list view it jumps down to the closest match in the body.

I'm looking at using the 'Go to Record/Request/Page' by calculation. Or something like that I think...

Any help?

Well, you can easily use a relationship. The only thing I couldn't understand is that the button must be clicked twice for it to work. It seems the first click just 'selects' it. So I put the same script-step twice and it works as it should (with just one button click).

Comment showed this technique for jumping in a portal. I've adapted it a bit for a list which is probably why it doesn't work as well.

What is particularly sweet is that you don't need to type an entire name - just whatever part you wish. And you can even have it fire from event trigger if you wish so User doesn't have to click a button but fires upon [enter].

Oh. And I had been playing with lines and autoresize. I liked the way the lines zoomed wider so I included that as well (even though you are on vs. 7 and can't use it now).

UPDATE: Corrected demo by commiting before GTRR.

GoToClose.zip

Edited January 15, 200818 yr by Guest

The only thing I couldn't understand is that the button must be clicked twice for it to work.

I think you need to exit the global for the relationship to register the change.

Oh now that made me belly laugh! And I haven't even checked but of course you are right! I'm laughing because I know better and have even started a thread about commiting under such circumstances. Ha ha!

I shall fix the demo.

Not working to well. I tried to simplify things for example sake....

The problem is in my reality the field of Last Name is actually 'Title' and it stops at about the 84th record for some reason every time!

I cannot replicate your issue. I have 168 records and can jump to the very end of them. Can you post your file? I would like to help you figure out why.

I wonder if the length of the text in the relationship match makes the difference, instead of number of records. I shall test that as well...

Edited January 15, 200818 yr by Guest

I have tested with 45 characters in the global and 45 characters in the fields and have added another 50 records. And I can still jump to record 240 consistently.

I wonder if there are some CHARACTERS which can trip it up.

UPDATE: I have testing with most characters that might be in a text field and can't see a problem with them.

Edited January 15, 200818 yr by Guest

Did you remember to sort the relationship? This is very important! Still, it doesn't seem to break it. And I'm testing on vs. 7 as well! Are you using 7.0v3?

try ...

Drop Dead, My Lovely [Hardcover] by Weiner, Ellis

I can't really post the file... to much in it and not enough time tight now to strip it down..

I do appreciate you help!

Edit !!

Ps yes on the version... no on the sort but will do

Edited January 15, 200818 yr by Guest

Does LaRetta's demo work for you? If yes, you didn't implement the method correctly in your file. If not, you have a system problem.

It works with that text and several records with similar, both with comma and bracket. With long lines in global with this text and also long lines in LastName (errr, Title, smile). It jumps 168 records down to it consistently. Maybe others can try as well - I can't make it break.

It does so it must be something I'm doing ..not doing correctly.

Will look at it some more............

Thanks guys & gals LOL

I wonder if there are some CHARACTERS which can trip it up.

I don't believe so, provided the correct language is selected for indexing. However, to add my own shot in the dark, both fields - the global and the name, er... the title - need to be Text fields.

What flashed to mind was unicode for the name, err Title and regular language for global text.

My first test said it doesn't break but now I've broken it and that's the only thing I've changed. I think case sensitivity breaks it. As you've said, language ... including unicode!

UPDATE: It could come in handy knowing this difference if you want to jump by case sensitivity ha ha!

Edited January 15, 200818 yr by Guest

FINALLY

Thanks a bunch. I deleted my table and script... started from scratch and PRESTO.

Edit I've never fooled with or quite understand how to 'event trigger' ??

Edited January 15, 200818 yr by Guest

I wouldn't call that 'breaking' - it follows the rules of the selected language.

I can't really post the file... to much in it

And you trashed it? I'm sorry you had to do that when it truly would have been better to figure it out - one item at a time! The answer was there. Ah well, I'm glad it works for you.

No, it's not breaking when it follows the rules of the language. Thank you for keeping me straight and narrow, Michael. It's important.

Still, it's cool that it responds to case sensitivity and a good thing to remember.

Edited January 15, 200818 yr by Guest

And you trashed it? I'm sorry you had to do that when it truly would have been better to figure it out - one item at a time! The answer was there. Ah well, I'm glad it works for you.

Noooooooooo, Would never do that!!

Also in case it was missed....I've never fooled with or quite understand how to 'event trigger' ??

PS I meant I trashed the self joining table and etc...

Edited January 15, 200818 yr by Guest

You can search here on Forums for 'event trigger' and 'plugin'. But in truth, I recommend against their use unless 1) the Developer is quite advanced and 2) there are no other native FM alternatives. They can bite even the best Developers. I know. :jester:

LOL...

Disregard !

Edited January 15, 200818 yr by Guest