nothing dangerous here. DEC VMS, for example, does it in exactly in the same 

The danger you seem to see (application sets a backup date, other app uses 
something different) is circumvented by supplying an old "full" backup to any 
incremental one for the programs to compare. In case you have none, the backup 
program will automatically do a full backup and initialise the time stamps.

Dangerous is when you use the backup timestamp for something else....


> Am 10.10.2018 um 00:38 schrieb Giorgio Garabello via Ql-Users 
> <>:
> 2018-10-09 17:26 GMT+02:00, Jan Bredenbeek via Ql-Users
> <>:
>> On 9 October 2018 at 16:44, Giorgio Garabello via Ql-Users <
>>> wrote:
>>> In the header file we have the backup date field from what is not used.
>>> Can not be used to insert us from file creation date?
>> Wouldn't this break any backup software?
>> I've written HARDBAK back in 1989 which uses this backup date to determine
>> if files have changed since the backup.
> :-O
> May I ask you why did you choose such a dangerous option?
>> And what do you mean with 'file creation date', the date when the file was
>> created on the medium or when it was last updated?
> when the file was created
> _______________________________________________
> QL-Users Mailing List

QL-Users Mailing List

Reply via email to