Change of File date and time without reading and new save

[Sunny]

Hi,

has anyone adaptet the dll call of 'SetFileTime' or is there another way to manipulate this value with LabVIEW?

Public Declare Function SetFileTime Lib "kernel32" Alias "SetFileTime" (ByVal hFile As Long, lpCreationTime As FILETIME, lpLastAccessTime As FILETIME, lpLastWriteTime As FILETIME) As Long

Regards,

Sunny

[zou]

Yup.  Take a look http://www.geocities.com/gzou999/index.html

[Oliver_Frank]

Hi all,

with a little help from my friends, i find out how to run the SetFileTime and GetFileTime function from the kernel32.dll.
The "G Toolbox" is a commercial product and wasn't a choice also the OpenG Toolkit they change there license away from LGPL.
You can find the VIs one the German LabVIEW Forum: www.labviewforum.de in this post (article no. #13; file: "kernel32.dll_Set_und_GetfileTime.zip").
You have to delete or replace the errorfunction because in my firm we use a variant for the error handling.

regards

Oliver Frank

[ControlsEh]

Hi Oliver. I saw your SetFileTime.vi on the German LV site. I was writing my own but have encountered some errors. Your vi is in 8.0 and I have LV2010-2012 but they are not installed. I use LV6.1 and don't want to install LV2012 because I want to keep my machines "clean" as I will be soon doing an installation test of my own LV app. I wondered if you could send me a couple png's of the BD and of the Call Library Node configuration please. That would help me a lot.

[johnsold]

Oliver has not logged onto the Forum for almost five years.

Lynn

[Dennis_Knutson]

You can simply post the 8.0 VI to the down conversion board.

[ControlsEh]

Thanks guys, I'll try that.

[ControlsEh]

Here are updated versions in LV6.1. You can set the Creation, Access or Modification Date with a cluster or LV seconds (U32) in UTC or local time.

[ControlsEh]

I changed the Generic acces rights from GENERIC_ALL TO GENERIC READ | GENERIC WRITE because I was getting errors over a network. Here are the final versions.

[rolfk]

---

@Oliver Frank wrote:

The "G Toolbox" is a commercial product and wasn't a choice also the OpenG Toolkit they change there license away from LGPL.

---

What could the issue be from changing from LGPL to BSD? If anything BSD is much more permissible. It "only" lacks the requirment to seperate the VIs out of a build executable when you want to distribute said executable.