How would solve this problem:

The user has a list of numbers to find. I have created a script that creates a new request every time the user type a number (in the number field) followed by Enter: if the number is left blank and the user press Enter, it is the end of the list and the find is executed.

What the user is asking is: "Of all the numbers I have entered, which one has not been found?"

The user can retreive the last find and get the list again, but it does not help him to know if the number exists or not or if any has been mistyped.

I can compare the number of find requests with the number of records found but it won't tell me which ones were missed.

Short of executing a find for each number, is there another way to get what numbers have not been found?

I dont think this is possible without using some kind of loop that goes through a list of all the search criterias and captures the find request into a log field if no records are found or using a relationship to determine if there are matching records.

Hi mf:

Your topic is a bit abstract, but intriguing nonetheless. I'll take a shot. Attached please find an example file that's rather abstract in its own right. I focused on the elements below ...

The user has a list of numbers to find.... What the user is asking is: "Of all the numbers I have entered, which one has not been found?" ... Short of executing a find for each number, is there another way to get what numbers have not been found?

The example shows how this can be achieved through relationships and without scripting. Using a global field, we can isolate the child records in one relationship that match the numbers entered in the global filter, yet also display through a second relationship the "stray" children. A constraint of this model is that the global filter field must be a Text field so we can enter a list of values separated by carriage returns.

I couldn't tell if this is what you had in mind, but I hope you'll find a way to apply its concepts. :twocents:

FoundAndStray_01.fp7.zip

Thanks for your demo file: the magic of relationships...

It may seem abstract (probably because I don't describe very clearly) but for the user it is quite concrete.

When they have a long list of number the are looking for, it may take them just as long to double-check their entries. It is particularly useful for typos and for records that are not yet in the system.

It has lots of potential. Thanks again.

MF

You're quite welcome, MF! I'm happy if it simply sparks some ideas for you. And I think you're right ... relationships are almost like magic. It seems we can solve many problems through the relationship graph, nowdays. They're probably my favorite hammer.

Additionally, from that "stray children" portal, we could use a Go To Related Records script/button to take users to the "stray" set. Some useful options could come out of that....

Ring back if you have any questions. :beer:

The users love this solution, except...

How do we make the Enter Key of the numerical keypad behave like the Enter/Return Key of the main keyboard?...

The numerical keypad Enter stops the data entry in the field. The Enter key on the main keyboard does a line feed (this is what I would like the other one to do). This field is setup to go to the next object only with the Tab.

The users have the option of entering a space, a comma or a dash to separate the numbers, but it seems like having the Enter key to work would make this whole solution just perfect...