Non existing folder is not created
Non existing folder is not created
Hello Igor,
I used beta-version 1101 to Synchronise two directory structures, including subfolders.
If on one side a new subfolder exists, containing files, and it does not exists on the other side, it will not be created. Synchronize seems to copy the files to the new folder, but here no folder is created, and hereto no files are copied. The files are copied to the root of the own drive.
Gerrit
I used beta-version 1101 to Synchronise two directory structures, including subfolders.
If on one side a new subfolder exists, containing files, and it does not exists on the other side, it will not be created. Synchronize seems to copy the files to the new folder, but here no folder is created, and hereto no files are copied. The files are copied to the root of the own drive.
Gerrit
remark
I am at work now on a Hungarian Win 2000 SP 4 and here it works.
What was strange is that it did not dislay the folder names in the preview window. So on the target side (hard disk) the folder names of the folders to be created where not displayed in the 'treeview' that displayes both folder names here at work properly. I'll send a screenshot ant the end of the day.
G
What was strange is that it did not dislay the folder names in the preview window. So on the target side (hard disk) the folder names of the folders to be created where not displayed in the 'treeview' that displayes both folder names here at work properly. I'll send a screenshot ant the end of the day.
G
I need to correct my last post slightly. Sometimes it works, sometimes it doesn't.
I just created 3 nested folders with data files in the bottom folder. When I synchronized that with a similar top folder (empty, no nested folders) in another drive, the program worked perfectly. It created the new nested folders and put the data files in the bottom folder as expected.
Then (settings unchanged) I attempted a synchronization of a more complicated directory structure. This time the program did not create the new, nested folders, but moved the data file into a completely inappropriate folder in the target directory.
I just created 3 nested folders with data files in the bottom folder. When I synchronized that with a similar top folder (empty, no nested folders) in another drive, the program worked perfectly. It created the new nested folders and put the data files in the bottom folder as expected.
Then (settings unchanged) I attempted a synchronization of a more complicated directory structure. This time the program did not create the new, nested folders, but moved the data file into a completely inappropriate folder in the target directory.
I'll download that and give it a try. I'm experimenting before purchasing.
Here's the latest, and it's a lulu...
I wanted to synch items in nested folders on different drives. The target folder didn't exist so the program wanted to put the files in a completely different folder.
Okay, so then I created a target folder with the same name (Powerstrip). This time the program wanted to put the files in yet another folder, but with a closer name (Print migrate). Huh?
So then I manually copied the Powerstrip folder into the target location and manually emptied the files in the folder. So now the names have got to be identical - no chance of any misspelling. Did it work correctly? Nope. It still wants to move them into the "Print migrate" folder.
Sigh. I'll download the old program and try that. Back soon...
Here's the latest, and it's a lulu...
I wanted to synch items in nested folders on different drives. The target folder didn't exist so the program wanted to put the files in a completely different folder.
Okay, so then I created a target folder with the same name (Powerstrip). This time the program wanted to put the files in yet another folder, but with a closer name (Print migrate). Huh?
So then I manually copied the Powerstrip folder into the target location and manually emptied the files in the folder. So now the names have got to be identical - no chance of any misspelling. Did it work correctly? Nope. It still wants to move them into the "Print migrate" folder.
Sigh. I'll download the old program and try that. Back soon...
It is October now - Is this problem taken care of?
Does it still exist in later betas of Version 3?
What is the status?
Thanks
WiseMax.
What is the status?
Thanks
WiseMax.
Test yields good results.
I spent all afternoon today using this version 3 (rel. 1.0.1145) and I am glad to report that this issue did not occur. There were many synchronizations where it was put to test and even without any coonfirmation it went rather well.
The matter seems taken care of then. Good job!...
The matter seems taken care of then. Good job!...