Got 'um, thanks!
Don't sweat it Bruce. There are duplicates in almost every batch. There is really no easy way for you to know if someone else has posted a internet serial number at some other time. Just keep your own submissions clean and leave the rest to me.
In most cases the dupes fall out when I paste the processed file into the main database table. When dupes occur at that point, they wind up in a "paste error" table and I can compare that to the main table to see why they fell out. What happened with last month's file is the duplicates were in the file that I compile from these posts. When I process the serial numbers, that file appends to a table. Dupes or other "key violations" are just deleted by Access and there is no trail, they are just gone and I have to figure out why they were rejected.
- Pete
Cheers Pete, with so many pairs of eyes on screens now you must get duplicates.....using the AK search panel often fails to find my test searches on my own entries. Is there a better way to 'test' the water so to speak to see if another AKer has been there?
new find;
Don't sweat it Bruce. There are duplicates in almost every batch. There is really no easy way for you to know if someone else has posted a internet serial number at some other time. Just keep your own submissions clean and leave the rest to me.
In most cases the dupes fall out when I paste the processed file into the main database table. When dupes occur at that point, they wind up in a "paste error" table and I can compare that to the main table to see why they fell out. What happened with last month's file is the duplicates were in the file that I compile from these posts. When I process the serial numbers, that file appends to a table. Dupes or other "key violations" are just deleted by Access and there is no trail, they are just gone and I have to figure out why they were rejected.
- Pete