12-11-2006 04:32 PM
12-12-2006
11:16 PM
- last edited on
06-19-2025
09:06 AM
by
Content Cleaner
Hello,
Welcome to the forums!
Does the executable behave this way on the same computer that you built it on? I can't think of anything that would strip a timestamp and leave everything else intact. I suggest building a debuggable executable, for which you can find information in the LabVIEW Help. This will let you probe the execution of your application at the point where the timestamp should be inserted - I suspect that doing this will show you pretty clearly what's happening. I assume the problem is in writing the data to the file, so verifying that the timestamp is generated and appended to the string being written should be all you need. If I can be of any assistance, let me know!
12-12-2006 11:23 PM
12-13-2006 04:12 PM
12-14-2006 01:48 AM
12-14-2006 08:49 AM
SORRY!!!!!
I will give it a try. Any idea why my carriage return/line feed was also lost? I can understand the time stamp, but why also the CrLf?
Thanks
12-14-2006 09:02 AM
12-14-2006
10:01 AM
- last edited on
06-19-2025
09:07 AM
by
Content Cleaner
Hi Marc,
I think you just got lucky, because the problem showed a correct timestamp, but in the wrong formatting. It is explicitely stated in the string from timestamp help that certain formatters are localized (%c, %x, %X, %z, and %Z).
Moreover the CRLF can be part of the timestamp (it can contain any other string)
Ton
Message Edited by TonP on 12-14-2006 05:02 PM
12-14-2006 10:19 AM
12-14-2006 02:31 PM