Companionlink 7 Build 7010 in Memory

[bmac]

I do not have CompanionLink automatically start with Windows 10. When I want to make sure that my Outlook 2016 the file is properly synchronized with DejaCloud, I manually start CompanionLink to synchronize to DejaCloud and then when I close Outlook, I also close CompanionLink. However, CompanionLink remains as a process and every minute continues to open the Outlook PST file to, I assume, attempt a synchronization with DejaCloud. Then it closes the PST file. This produces a new timestamp for the file and as such, dropbox thinks the file has changed so it attempts to upload the changed file to the dropbox cloud.

When I close CompanionLink, it should eliminate the process as well.

Why does this matter to me? I synchronize Outlook 2016 between two computers -- my desktop and laptop. If CompanionLink on the desktop continues to be active, then dropbox produces what is called a conflicted copy of the PST file. This causes a number of issues if I am already using Outlook on the laptop which has already loaded the PST file.

Is there a way CompanionLink can be configured that when it is close, it also closes the process?

[DJOCTO]

bmac, in CompanionLink Settings, Advanced Button, Auto-Synchronization, set it to Manual Sync. When in Manual Sync mode the agent will not need to check Outlook.

All other Auto-Sync settings will open Outlook periodically to check for changes.

[bmac]

Thanks CTO. But would it be difficult to terminate the windows process at the same time CompanionLink is closed? I do not mind setting it to manual sync, but I prefer the pushsync - as sometimes I forget (old age!).

[DJOCTO]

Push sync requires CompanionLink to be open, and also Outlook.

I guess I'm not clear on what you are wanting. The Icon represents that CompanionLink is active. I.e. it is checking various processes.

Is your issue more that it is checking Outlook too often when Outlook is inactive? We can look at this.

[bmac]

Yes, it is actually opening the PST file and checking it every minute. This is after Outlook as a Windows application has been closed by the user. The problem with CompanionLink doing this is that I may have Outlook open on the laptop. Both the desktop and the laptop share the PST file stored on dropbox and if the PST file is in use on the laptop but CompanionLink is checking the PST file on the desktop, dropbox will produce a conflicted copy.

[DJOCTO]

Ok. I wrote this up as a "Idle Process" should not open Outlook. I'll work it out with the developer.

The key here is the local file, but for you it's not really local but tied to dropbox.

For Exchange files, we need to check if Exchange has modified the contents. But for a local file we should be able to check the file date/time to see if there are changes.

[bmac]

Thanks for your help CTO!. I look forward to the update.

[bmac]

CTO - just wondering if a new build will be available with this issue fixed? Is there an in house build site for companionlink as well?

[Eagle 3]

I do not have CompanionLink automatically start with Windows 10. When I want to make sure that my Outlook 2016 the file is properly synchronized with DejaCloud, I manually start CompanionLink to synchronize to DejaCloud and then when I close Outlook, I also close CompanionLink. However, CompanionLink remains as a process and every minute continues to open the Outlook PST file to, I assume, attempt a synchronization with DejaCloud. Then it closes the PST file. This produces a new timestamp for the file and as such, dropbox thinks the file has changed so it attempts to upload the changed file to the dropbox cloud.

When I close CompanionLink, it should eliminate the process as well.

Why does this matter to me? I synchronize Outlook 2016 between two computers -- my desktop and laptop. If CompanionLink on the desktop continues to be active, then dropbox produces what is called a conflicted copy of the PST file. This causes a number of issues if I am already using Outlook on the laptop which has already loaded the PST file.

Is there a way CompanionLink can be configured that when it is close, it also closes the process?

How are you closing CompanionLink? The X button does not close CompanionLink, it just minimizes to the System Tray. To close CompanionLink either File>Exit or right-click on the icon in the System Tray and slect Exit.

[bmac]

convenient

I was closing it using the windows red X. You are right that if I close it with the file/exit, the process closes as well.

But I still think it would be more convenient -- for the user -- if the CL process didn't open the PST file if the file date/time does not change from the time before.

[DJOCTO]

bmac I agree. However, we don't actually interact with the PST file. The "Outlook System" is a .Net connection in memory. And there are no details in the API to know the date/time for the PST file.

Outlook is not Palm Desktop.

[bmac]

Just wondering if the developer has considered this request to have CL, if it is open, to ignore the PST file, if the file date/time has not changed.

[bmac]

CTO - I just happened to download the latest beta CL and noticed that it now has a command in settings to '...Not autosync' when Outlook is closed. I believe that solves my issue of CL opening Outlook on my desktop to see if anything has changed when in fact I am using Outlook on my laptop (Surface) where that would produce a conflicted version in dropbox. Thanks for this!
Bill

[DJOCTO]

Yes, I think that is because of this thread. I'm sorry. I should get better at tracking back. It takes several weeks on a given request, and we handle 3-5 requests a day from forums, emails, telephone etc. So I find I lose track.