When a pseudo event is created prior to the season, it generates an event ID.
That event ID exists in the master back-end which is copied to both primary & secondary tablets.
When pseudo-events are converted to regular events, those events retain their Event_IDs.
RESULT: The same Event_IDs exist on BOTH the primary & secondary tablets.
During import, Event IDs that already exist on the master are not imported.
So, even if pseudo-events are archived & deleted from tbl_Events in the master, after the primary tablet import the secondary tablet does not import events that were originally pseudo-events because their Event_IDs already exist in the master database (they were imported when the primary tablet events were imported).
When a pseudo event is created prior to the season, it generates an event ID.
That event ID exists in the master back-end which is copied to both primary & secondary tablets.
When pseudo-events are converted to regular events, those events retain their Event_IDs.
RESULT: The same Event_IDs exist on BOTH the primary & secondary tablets.
During import, Event IDs that already exist on the master are not imported.
So, even if pseudo-events are archived & deleted from tbl_Events in the master, after the primary tablet import the secondary tablet does not import events that were originally pseudo-events because their Event_IDs already exist in the master database (they were imported when the primary tablet events were imported).