innodes Posted April 12, 2010 Posted April 12, 2010 I have a user that does not want the search results to not be resorted. She uses the add/request to build a search list. Because of other lists she needs to access, she would like the searched data to remain in the order she entered it. The problem is that the search seems to automatically resort. I don't have any sort functions scripted. Is there anyway to turn this sorting off?
bcooney Posted April 12, 2010 Posted April 12, 2010 Add unsort. FM10 retains the sort, if done once, "automatically."
innodes Posted April 12, 2010 Author Posted April 12, 2010 (edited) Thanks, but it doesn't seem to be unsorted. Here is what I have, the script enters find mode and searches from one button: If [Get(WindowMode)=0] Enter Find Mode [] Else If [Get(WindowMode)=1] Perform Find[] End If Unsort Records I enter 7j 5h and it returns 5h 7j Edited April 12, 2010 by Guest added screenshot
TheTominator Posted April 12, 2010 Posted April 12, 2010 (edited) The "Unsort" command will sort the records into the order that they were originally entered into FileMaker, i.e. the record creation order. It sounds like you want the found results to be sorted by the order that they were requested in the Find operation. That's much trickier. If you are scripting your Find, I think you may be able to do it, but it won't be simple. It may go something like this. 1) Memorize the sort keys in the multiple requests just prior to carrying out the Find operation. 2) Perform the Find. 3) Put the memorized ordered list of values into a value list. 4) Sort using the value list to specify the sort order. This presumes that the query is something relatively simple such as searching on a single name or a single ID. If the find requests are varied (request 1: find all females, request 2: find guys named Bob), then this method would be quite hairy. Edited April 12, 2010 by Guest
innodes Posted April 13, 2010 Author Posted April 13, 2010 I think I am just going to let this one slide. thanks
Recommended Posts
This topic is 5337 days old. Please don't post here. Open a new topic instead.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now