Changing the file not necessarily leads to a change in the file's size, but typically (i.e. unless a sufficiently privileged process has changed that) the following always happens:
- the "last modified" timestamp of the file is updated to the current timestamp
- the "archive" bit is touched (if it was not set, it is set by the OS automatically)
Robocopy would compare the "last modified" timestamp of the destination with that of the source and copy when these two differ (this behavior might be tweaked according to your requirements using the /xn
and /xo
switches). Robocopy would only honor (and reset) the archive
file attribute when you use /m
switch - see the robocopy documentation for details.
Thanks for all the helpful comments, finally I was able to figure it out :)
If anyone is struggling with a similar problem, here is how I did it:
First I contacted support. If you are stuck with an uncommon piece of software, contacting support is usually the first step you should take. They usually have the right answers.
An ODBC driver is what its name suggests, a driver and nothing more. For any kind of remote access you need some kind of server. Also, if you want to access a remote data source, you need the driver installed on your client machine (the machine your remote application will be running on).
So far so good. In my case I got the connection parameter description from their support but still couldn't figure out, how the connection string looked like. I tried everything, but nothing worked (I got strange errors, that were not very helpful, like "couldn't fetch error message").
Finally I found an answer in this post: dsn-to-connectionstring
Looks like DSN records are nothing more than name-value pairs. Connecting to the data source by using a DSN worked, but I couldn't use a DSN in my particular case. So I got the needed parameters by opening REGEDIT and, as suggested by the above post, opening up the System DSN location:
HKLM\Software\Wow6432Node\ODBC\ODBC.INI\
This is the location where 32-bit System DSN records are stored. If you need to find the 64-bit version, it is located here:
HKLM\Software\ODBC\ODBC.INI\
Sure enough, there was the system DSN I needed.
If anyone is interested in why I still didn't know how the connection string looks like, although I had the connection string parameter description:
To be able to connect to a remote server I had to add a "Location" parameter to the connection string. I tried adding the URL and/or IP of the server machine and it didn't work. By looking at the Registry I found out, that I actually have to add the IP, port and Protocol to a configuration file, specific for this ODBC driver. For the "location" attribute inside the connection string I had to specify the name of the configuration I added.
Best Answer
There are two ODBC dialogs on your system. One for 32bit and one for 64bit. The one you can reach via system control is the 64bit one.
The 32bit version is located at