What you are seeing is probably not duplicates. In fact, LOGic includes a timer so that if a station posts the exact same spot more than once within a five-minute period, the duplicate spots will be discarded. (This is done primarily to prevent duplicate spots from being processed when monitoring packet clusters in unconnected mode.)

If different stations spot the same station, the spots from all stations are shown. The Comment field of the spot is also used for determining duplicates. If the same station posts the same date but with a different comment, both spots will be shown.

LOGic's spot log, as set up from the factory, shows not only needed DXCC, but also CQ Zones, ITU Zones, and Continents. It can also be configured to show needed IOTAs and grid squares. If a spot is needed for more than one award, more than one spot record will be created. Make sure the AWARD and VALUE columns are visible! Otherwise, the spot log will display what looks like exact duplicates, when in fact they are not.

If you don't want to spot CQZ, etc., simply turn off spotting for these fields in tools/setup/log fields....

Even more spots records can be created by the SubAward(tm) feature. Suppose that you have LOGic set up to track QRP DXCC, and someone posts a spot for a country that you have never confirmed, QRP or otherwise. LOGic will create the normal DXCC record, as well as a QRP DXCC record.

Make sure that the Award Subaward, and Value columns are visible. This way you can see why LOGic generated "duplicate" spot records.

If LOGic is spotting awards that you do not care about, you can disable spotting of these awards. Consult the documentation.