Searching for calculated values

[balooka]

Hi - i seem to have a problem searching for values generated by a case-calc.

I have the startweek of a range and the endweek. Lets say the startweek is 4 and the endweek is 9. The maximum range is 25 weeks btw. The calc below generates a list of all weeks in this range using a simple case-function. In browse-mode it all looks fine but when entering the find mode and entering - lets say - 5 it doesnt find anything, as if the calc-results are not searchable.

The calc i use is:

Startweek & "

[BobWeaver]

It should work. Make sure that you define the result of your calculation as text, not number.

[Ugo DI LUCA]

Hi Balooka,

The case calc you've defined is just acting as a Multi-key. Instead of a classic find, you should drop a global field on the layout, and trigger a Go to related record script using a relationship your global::the multikey.

[Ugo DI LUCA]

Hi Balloka, Hi Bob,

The problem with finds in compounds keys is that if you were entering a "2", you will end to find even the 21,22,23,24,...

Unless there is a tip for that also.

Bob, BTW, congratulations for your date and number ranges samples

[djgogi]

Yes, there is.

You can insert search string in field cKey like this:

=2 =21

and hit find

The above would find every record, if any, having 2 21 in field cKey

Dj

[cjaeger]

Unless there is a tip for that also.

enter a "=2" (without the quotes)

finds only 2, not 21...

[cjaeger]

hi djoggi, you were faster ....

[djgogi]

Hi, cjaeger.

We have chosen the same numbers for example.

Just to add something else.

You couldalso mix criteria inside field like

=5 56 =123

dj

[Ugo DI LUCA]

Hi DJ and Cjaeger,

Thanks to both of you. Actually DJ came from nowhere (were you hiding here). BTW DJ, thanks AGAIN for the "conditional lookup tip". I was discussing with Christian some minutes ago.

Actually I messed up here... I quite forgot what a Perform Find is working with relationships.

As we are on this, how would you solve this, as you wil notice from the both post that they are controversial

solution 1

solution2

I don't know how she finally solved that ?

[djgogi]

Hi Ugo,

problems with cookies I think.

Do you see me now?

Dj

[djgogi]

Having text field alfa

Rec1>alfa=2B 3C 2 2A

Rec1>alfa=2 3A 2 2A

for ex.

Than performing find with

=2B

will give only rec1

The solution1 is the same thing

Dj

[djgogi]

Having text field alfa

Rec1>alfa=2B 3C 2 2A

Rec1>alfa=2 3A 2 2A

for ex.

Than performing find with

=2B

will give only rec1

The solution1 is the same thing

Be aware that == with find, means exact whole string and not exact word in string

Dj

[Ugo DI LUCA]

Hi,

Sorry I should have been more precise.

Record text = CustOrder200A

In order to find 200, I need to transfer it as a num.

---> Record num = CustOrder200A

Searching for 200A will also lead to 200B, 200C.

With all these conditions, I felt really like Perform Find was a bad idea, and rather use a global and GTRR.

[cjaeger]

text field, search for

*200A

[djgogi]

Hehe, this time Christian was faster.

Dj

[cjaeger]

to get really strange findresults, try searchin a multikey with a multikey:

1. copy the return from a text field

2. type your multi-criteria into one field, first request and separate by pasted return (typing will not work)

3. hit return key

STRANGE results ...

[Ugo DI LUCA]

Ok Guys, I stop here before I celebrate my N

[djgogi]

Well there is no need for carriege returns.

Simply put space between different request and you get:

AND serch in field

Dj

[djgogi]

What was to the original question?

Dj

[cjaeger]

I'd go for the text field. It

[Ugo DI LUCA]

Hi,

OK, these are very good tips

[cjaeger]

and now try TexttoNum("Y 2000").

[djgogi]

12000

2000

Dj

[cjaeger]

it should yield either

12000 or 2000 depending on your version of Filemaker.

TexttoNum("Y") is 1, even in FM 6

[cjaeger]

12000

Dj

Not im FM 6 , Mac OS X

[djgogi]

It is 12000 in first case and 2000 in second

PS I have ******* slow conection in this moment

[Ugo DI LUCA]

Hey,

And I finally got lost here with your Y, "year", 2000, 1 2000....

Right it's 2:00 in the morning for us in Europe, and I may need more rest than you Gurus.

[cjaeger]

same with me - slow connection.

Year => 1

Year 2000 => 2000

Year2000 => 2000

They must have changed the algorythm im FileMaker 6.

In Dev 5.5 it is still as with yours.

Still, we do have to escape every Occurence of Y, N , T, F before doing a TexttoNum (lowercase also).

Checked on a File with ASCII Codes0-255.

[cjaeger]

Right you are , Ugo

It's 2 am for all 3 of us here..

Let's call it a day.