Foundsets are our friends - or are they?

Classic Servoy
1

Before importing data from a legacy application I want to look for duplicates and let the user decide on what to keep and/or merge and what to throw out.

Somebody once told me that foundsets are our friends, so I came up with this:

I go to the first record start searching for duplicates.

If there are duplicates, I put them in a foundset so the user can do his thing. I invert the foundset so I have a basis for the next search - I don’t want to search records I already know are duplicates.

If there are no duplicates i go to the next record and search again.

Until all records are searched. Great!

I have 500 addresses in the table and if I invert a foundset of let’s say 18 duplicates, I end up with a foundset of 482 - which is impossible because of the 200 limit. Not so great…

Question 1: Am I right in my assumption that this method will not work because of the FS limit?

Question 2: Is there a workaround? Am I missing something?

Question 3: Can addFoundSetFilterParam help?

Question 4: How permanent is addFoundSetFilterParam? How do I ‘unfilter’?

2

What result do you want? A foundset with the duplicates? So that they can delete those? Or do you want the foundset without the dups?

If the latter then i would tag those records and then do a query ..

3

Both. First I need the duplicates FS so I can tug them away for later processing by the user and then I need the inverse FS which I would use as the base for the next search. I gather that that is indeed not possible becasue of the FS limit? Please advise.

I have tagged away the last hour or so and the solution is working now. The foundset way would have been more elegant IMO and I wanted to make sure that it is a dead end before I dropp it completely.

Thanks for the help. It’s Miller Time! :P