EFU files use the Windows FILETIME format in decimal.
EFU files also support ISO 8601 dates.
However, when saving from Everything, EFU files always use FILETIMEs for performance reasons.
FILETIME
Contains a 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601 (UTC).
Hi, I would use your advice:
Convert FILETIME To Unix time: https://stackoverflow.com/questions/616 ... unix-linux
if only it would be useful for me. But it is not. I am not skilful in C+ (referred to on the site advised by you), and – first of all – I need to use EFU file in MSAccess (VBA/SQL), in which I am quite skilful. The number of digits in UTF date exceeds the limitations imposed by Microsoft on MSAccess operations. Are there any freeware converters or VBA/SQL procedures to convert your UTF data format to standard formats or Unix datetime format?
Your advice will be greatly appreciated.
I'll look into making a script or tool to convert the EFU filetime format.
For now, there will be a switch in the next Everything version to save the time as ISO 8601 (UTC) or ISO 8601 (with timezone)
If you would like to try this now, please check out the Everything 1.5 alpha.
To change the efu filetime format:
In Everything 1.5, type in the following search and press ENTER:
/efu_filetime=x
where x can be one of the following:
0 = FILETIME as decimal.
1 = ISO 8601 (converted to UTC).
2 = ISO 8601 (with time zone offset).
If successful, you should see efu_filetime=x in the status bar for a few seconds.