Wrong dates on files

[dcol]

I am a registered user of TC running 9.51
In sub-directories of network drives, the displayed date does not match the actual file date. Shows correctly in Explorer.
I have the refresh options set correctly. Even if I delete a file on the server it does not go away in the TC directory.
Even if I delete a file and copy it back, the date is then shown as the copied date when actually the file date has not changed on the server.
Seems the date displayed in TC is the date the file was first displayed and keeps that date indefinitely.
How can I purge the history or refresh so the directories show the correct date?

[Dalai]

Well, from your description, I get the impression you're looking in the wrong directory. Try copying the directory's path from Explorer's address bar into TC's location bar (the one that shows the path), or TC's command line (you need to prefix it with "cd ", otherwise TC will open that dir in Explorer).

Regards
Dalai

[dcol]

Thanks for the reply
I already tried that, but I now know why it did it. I use custom columns and set creationdate instead of writedate for the date field. Man that messed me up, why would anyone use creationdate?

[Dalai]

That explains the "wrong" date, but not the portion about the deleted file(s) still showing up.

why would anyone use creationdate?

You're not seriously asking this quesion, are you? Files have three different timestamps. The creation date, as the name suggests shows when a file was created on a volume. Sure, the modification date is used far more often (which is why TC shows that by default in the date column), but believe it or not, people do consult the creation date.

Regards
Dalai

[dcol]

I was also surprised about the deleted file still being there. I tried deleting the 'phantom' file and it gave me an error, but did not go away. I put the file back, then it deleted fine. Not sure what that was all about. I suppose the creation date may be useful in a rare circumstance, but I would rather see when a file was last modified, not created.

[gdpr deleted 6]

I was also surprised about the deleted file still being there.

Without knowing your actual setup, allow me a wild blind guess. It could perhaps be an effect of the SMB client-side cache. You might try setting the following registry parameters on your client machine (no, not on the server). Keep a backup/note with their original state, so you can easily roll back the changes in case they don't help:

Code: Select all

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\LanmanWorkstation\Parameters]
"DirectoryCacheLifetime"=dword:00000000
"FileInfoCacheLifetime"=dword:00000000
"FileNotFoundCacheLifetime"=dword:00000000

I don't recall whether the machine needs to be rebooted or what service(s) restarted after applying the registry changes. So, to be sure, reboot your machine after applying these settings

These settings will effectively disable the SMB client-side cache. But it can also cause increased traffic between the client and the server, which can lead to a performance decrease depending on how exactly you (or the programs you are using) are accessing stuff on the server.