Great people: please come and study how to avoid duplicate catalog extraction
- December 20, 2024
- 2 replies
- 1138 views
Last time I found catalog duplicates being extracted.
The main reason for this was that some of the tables themselves did not span a page, they were only on one page, but the “Skip Header Rows” was used.
In this case the table of contents at the back was wrong.
If there are very few tables, I can remove the “Skip Header Rows” for those tables that do not span pages.
However, there are a lot of tables that need “Skip Header Rows” at the beginning, and after the client rewrites them, these tables do not need this feature because there are a lot of them, and it is difficult to recognize the cancellation.
In short, if there are hundreds of tables, you will go crazy, the catalog is all wrong.
Please research if there is a simple and workable solution for this.
Thanks

