Why does it take so long to update my card?

Principalm may take a long time to update if your files are stored on the network. Please make sure you are running the latest version of Principalm

The issue that you are experiencing on your network is not necessarily related to the speed of the network, but how the transport protocol used on the network operates. Principalm Connect does not process the files multiple times but does do partial file reads and uses rewind on the imported files in some cases. Some network types experience poor performance under such circumstances.

If you are running the latest version and still experiencing extremely long card updates this may be due to the fact that your set up is scripted to run an export once per night, which will trigger Principalm Connect's import every day, the first time Connect is run. Essentially this will take the same amount of time as a full rebuild.

This is a problem we've been planning to address for a while, although it is not a simple problem, because we could have conflicts between the program running automatically and the program running at the user's command.

We have a partial workaround for this problem in the current version of Principalm, where the user is able to script their Connect import to run overnight, similar to how some of the bridges work now. Please see the User Guide for more information.