Yes, I do open a sequence file through the API with the method Engine.GetSequenceFileEx as a sub step to a customized sequence call step. I have now modified this sub vi with the method "Engine.ReleaseSequenceFileEx", and the warning has disappeard.
My aim with the customized sequence call step, is to get the sequence file version (Data.Version) of the seq file I call. (Attached is the post vi I use) It works fine, but the post vi shows to be a bit of a bottleneck when it comes to time critical seq files. Do you think this is the best way to get the seq file version? Any other suggestions?
Thanks
Regards
Tom Andres Lomsdalen, CTD