Just to clarify, you should be using 3 periods "..." to define a range, not two ".."
Thanks. The FileMaker manual said you could use 2 or 3. I've tried it both ways.
Ah, OK. Have you tried omitting the AM and PM parts from your search query? Just using 24 hour notation?
Yes. As a matter of fact, when I first tried the search I had forgotten about the AM and PM so I had searched without it. That didn't work.
... and just to clarify, the field type your searching in is definitely set to 'Timestamp' ? One thing that might be worth trying is searching for a date and time range where the date and month portions are both lower than 12, that rules out any formatting issues...
What is the exact error you're getting? Or is there no error and just no results?
Yep, that's weird. I've been stumped a few times by searched on Timestamp fields, but usually I can resolve it by trying different combinations of re-arranging the dd/mm/yy mm/dd/yy format, but you've already tried that.
Out of interest, what if you search using the greater than ">" or less than "<" operators? Same problem?
What do you mean by "external source"?
Is this a FM table or an ODBC table in the FM database?
I can't recreate the problem. Try Records>Modify Last Find to see if that provides any hints in the find criteria.
It's a good idea to check what FMP is using for the Find criteria.
After performing the Find and getting the error dialog select "Find Again" (command-r) to see how FMP has altered the Find criteria. It should be exactly as entered.
However, since you didn't put the seconds on the end of the second timestamp value it should have added the wild card character, star (shift-8), to the time value.
...6/30/2017 11:59:* PM
If it didn't then the field is not recognized as a Timestamp.
As a test I suggest you try putting in the lower and upper dates and leave off the time values. For example using the "//" for today's date. FMP will add the time as "// *:*:*".
That is one way to discover if FMP is treating the field as a Timestamp.
Potentially there could be a corrupted data index. Turn off all indexing for the field. But, leave the option to auto-index turned on. Then do a Find in the field and let FMP reindex it.
Thanks everyone for your help. I wasn't able to solve the problem using any of the solutions. In the end, I just exported all the records, sorted by the timestamp, and deleted the ones before and after my range.
You never answered my question about what the "external source" was.
Without knowing your environment, it can be impossible for folks here to help and try to reproduce the issue you're facing.
HOPE THIS HELPS.
It was another FM table.
What I think you should do in situations like this when nobody here can reproduce your issue is to create a small separate FM solution which demonstrates the problem and post it.
There must be something obvious going on that should be easily fixed.
Given this set of records:
And this "Find" condition: 1/2/2014 *:*:*...12/31/2015 *:*:*
That is what I would expect since the times are wild-carded. I created a possible problem "edge case" with 12/31/2015 at midnight, but FM did not get confused.
If you don't want to post a FM solution which documents the problem, then document something like the above. Post your actual find conditions and screenshots of your results from FM.
Your issue has gotta be something simple or this forum would be nothing but complaints about this issue.
HOPE THIS HELPS.