What the `a' switch actually does is decide whether or not to perform the following test in deciding whether or not to back up the file. The test: was the previous version of the file newly created attached to the global file specified? If a is TRUE (the undocumented default), then the test is performed. As a result, in order for foo.bar to be backed up (if one has the profile entry AutoBackUp.Files: -a [User]<Yourname>foo.bar), the previous version of the file must exist on the local directory, and must be an attachment to the global file [User]<Yourname>foo.bar. It is sometimes possible to break these connections, and once broken, they remain broken because AutoBackUp doesn't. I normally use -~a, on the other hand, which solely requires that the short name of the newly created file match the short name of the global file in the profile. This is definitely playing more fast and loose, but is much more impervious to broken connections. For reasons which are vague in my memory, d TRUE must assume a FALSE.