FreeFileSync Forum

Since you aren't the developers at all Plerry and xCSxXenon (I don't know if you are programmers at all) I won't address you anymore.

I apologize to the actual programmer @Zenju. Thanks Zenju for creating a great tool. And maybe you can read over this post and do with it whatever you like. For ...

If you actually read my post, you've seen that I told you that the proposed solution doesn't work in my case (as well as others that have been dismissed by the same arguments, I've read on the forum). In my case it is not possible to create a symbolic link to the source. Some others couldn't as well ...

I have actually read through them, its a pretty poor explanation, and never was there actual detailed insight provided into what was in the db files. The so-called work around with symbolic links doesn’t work in my situation (as it wouldn’t work with others that were dismissed also).

It’s clear ...

In stead of continually telling people that this is not possible, and do nothing, it would be great and more helpful to actually implement a solution. I see absolutely no reason why this isn’t possible.

I know.
The point is that people want to turn the feature ON (not off).
My solution would make it possible to actually use the feature even if the sync.ffs_db file cannot be written to the source folder.

Now, the sync.ffs_db files need to be written to source and destination folder.

But sometimes one doesn’t have write-access to the source folder, and this entire feature becomes unavailable.

Please make it possible to put the source - sync.ffs_db file elsewhere. Other people have asked for this ...