First check out this thread for examples of scripted finds. Note how fields with global storage are used in these examples: Scripted Find Examples
In FileMaker finds, any criteria specified in the same find request is an "and" type find. If you specify "red" in a field named "color" and "25" in a field named Quantity, then perform the find, you find all records with "red" in the color field and 25 in the quantity field. In your case, a scripted "and" type find need simply have two set field steps, one to specify criteria for the first field and one to specify criteria for the second.
An OR type find finding all records that have red in the color field OR 25 in the quantity field takes more scripting to put each criterion in a separate request or to perform successive finds with
ConstrainExtend found set used in place of Perform Find after the first Find is performed.
To get the layout that you describe, you can set up a list view layout and put your two global, formatted fields in the header. You can use script triggers on these fields or a button in the header to perform the find.
In the body of this list, you'll see the records found by the scripted find and you can either place a button in the layout body or select all fields in the layout body and use button setup to turn them into a button. Either such button need only use Go to Layout to go to a different layout set up for a detailed form view of a record from the same table to enable the user to select a record pulled up by the find to see it on the detail view layout.
You can even add script steps that count the number of records found and that then switches automatically to the detail view if only one record is found.
Thanks Phil thats really appreciated :)
Note: spotted pretty serious error in my previous post and edited it to correct it.