|
A few things. 1. How do you know this timestamp field is becoming garbage? Perhaps the field is fine, it's just the way you are displaying it? Or are you looking at the field in debug? 2. You could be overflowing a varaiable on the stack right next to this timestamp which is overflowing into the timestamp field. Take a close look at any pointer type usage you are using in your program. If the field is actually becoming garbled, this is the most likely cause. HTH Regards, Jim Langston -------Original Message------- From: rpg400-l@midrange.com Date: Tuesday, October 23, 2001 11:43:09 AM To: Rpg400-L@Midrange. Com Subject: Corrupted timestamps? This is a multi-part message in MIME format. -- [ Picked text/plain from multipart/alternative ] I'm using a timestamp (type "Z") field with INZ(*SYS) to stamp added records. Somewhere in the program (my debug Watch says it happens when I CHECKR on a completely different field) the timestamp becomes garbage and ends up looking like this: '01-10- 23-10.16.42.927000' instead of '2001-10-23-10.16.42.927000' This is a production program. Has anybody else experienced this problem? Thanks, rf
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.