HeaVy

Hi, "I assume that you are creating a new file, then calculating an MD5 as a checksum. Try to use the file path out of the write characters to file as the input to the MD5 function to enforce data flow." I was checking the MD5 of an existing file, not creating a new one. First I checked it with the MD5 ComputeHash.vi and once the VI was finished with execution I tried to open it with the Open/create/replace File.vi which produced the error code 8. Two other guys tried to figure out as well what's going on, but we got nowhere. However, we made an MD5.dll with C and that's working just fine so no problems anymore. Thanks for your help.

Hi, The MD5 ComputeHash.vi is a handy tool indeed, but there is one problem that I haven't been able to solve. If the MD5 ComputeHash.vi is a sub-VI within your application and you first execute it and then try e.g. to open the same file that was used by the MD5 ComputeHash.vi, an error is produced (Code 8: File permission error). For some reason the file cannot be accessed or edited until the execution has stopped completely. Don't know why this happens, but I wonder if the .NET functions have got something to do with this even though the references seem to be properly closed. Any ideas how to get rid of this problem? LabVIEW 8 is no solution since 7.1 is still the default environment in this case. Thanks.