"... you mean these fans?" Posted July 14, 2017 Posted July 14, 2017 Hi, I have solution on a network server. After some forum suggestions we started finding and navigate our layouts under a "zero" record condition. Only showing records that are required when required. When I am in a condition within our scripts to "Delete" the found set, I have noticed that instead of showing "Zero" records after the script deletes ... FileMaker dumps all the records that were not in the found set, which can be significant in some tables ... ?? So I would see 23 / 5000 Found ( Sorted ), then the script deletes, to 4977 Total ( Unsorted ). So what is going on ?? any insight, can I prevent FileMaker from doing this ? Thank you.
comment Posted July 14, 2017 Posted July 14, 2017 You could delete them one-by-one in a loop. I can't think of any other method at the moment.
LaRetta Posted July 14, 2017 Posted July 14, 2017 (edited) One possibility ... Go to your layout with zero records Perform your find Open a new window Perform Delete All Records Close your window This should leave you with your 0 record state. Of course it still fetches those needless records but at least you've back to 0. I suppose you could instead Show Omitted so I doubt this will help. Edited July 14, 2017 by LaRetta
Recommended Posts
This topic is 2742 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