..confusing find script

[Genx]

gday gday, i know everyone loves me and my wonderful questions so ill just get down to the point lol :...

basically... when a user clicks my find button... i.e. not native filemaker... a script is executed that has to first omit all records that have one of two different values in a specific field.. then it lets the person search as normal... through all the remaining records... im not that great with the constraining and extending options ..

could someone please produce me a mini script or tell me how to get around omitting those records using some other function please?

Thanks lots, as always in advance, genx

[VICH]

if you have them type their search request into a global...

then perform a find on the one of two values

then constrain found set, and make it equal to the global...

that should work

OR

make a find script where it goes like this

enter find mode (pause)

perform find

loop

if(value1or2 = 1)

omit record

goto record request first

else

goto next record exit after last

end loop

something like that and it will flow as if it were just one search

Edited January 31, 2006 by Guest

[Genx]

hmmm omit loop... never thought of doin it that way.... cheers

[Søren Dyhr]

im not that great with the constraining and extending options

If you were - would you see, how ignorant the first reply is! Although his point in reversing the order is alright.

Enter Find Mode[Pause]

Perform Find[]

Constrain Found Set[Restore]

...where you inside the last line can build in as many omitted requests to skim the records you wish for, to sift through the process. So please no more looping!

And while we're at it please notice how fully fledged ranges have become:

Some of the new date search features in FileMaker Pro 8 are just what I've always wanted. For example, you can type in a range of "Monday...Friday" or "Mon...Fri" to locate all weekday dates. Or, you can use wildcards to locates all dates on January 1st regardless of the year by typing "1/1/*". You can also use curly brackets to specify a range of months such as "{1...6}/*/* to locate all the birthdays in the first 6 months of the year. Try these same techniques with time fields like wildcards. Play around with these tools and I'm sure you'll be impressed with the flexibility. Let me know if you figure out some combination of these new features that let's you accomplish some really cool technique.

....snipped from: http://www.databasepros.com

--sd

[Genx]

all i wanted was to let user search, then hide those where the values stored in a particular were equal to "a" or "b"... i dont have trouble with the actual find script with the pausing and the what not, i just wasnt sure how to get rid of the records where the field was equal to a particular value as opposed to constraining.. hope that made sense, the help would be appreciated as i understand how long a loop script could potentially take with an increasing number of records...

cheers, genx

Edited February 3, 2006 by Guest

[Søren Dyhr]

the help would be appreciated as i understand how long a loop script could potentially

It was meant as such ...but can you see how to stack omitted request inside either Perform Find or Constrain Found Set - You leave a sense of uncertaincy here - But again I could be mistaken???

--sd

[Genx]

yeh, its all good, thanks for the help

genx