| 
 | 
Francis Lapeyre (flapeyre@COMMUNIQUE.NET) wrote:
>Kahn, David wrote:
>>
>> The TIME opcode requires a numeric result field. Crazy though it
>> sounds
>> you cannot TIME straight into a timestamp field.
>
>TIME to a timestamp field works, all right, but only if you have V3R7.
Thanks for the information, Francis. We're still stuck on V3R2 for the
time being. It does seem as though a timestamp should be a natural
target for TIME - saves all that messing around. Another incompatibility
between V3R2 and V3R7. Don't tell Dave M .  :-)
Dave Kahn - TCO, Tengiz, Kazakstan
=========
e-mail:  kahn@tengizchevroil.com    (until September 30th)
         dkahn@cix.compulink.co.uk  (from  October 1st)
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MAJORDOMO@midrange.com
|    and specify 'unsubscribe MIDRANGE-L' in the body of your message.
| Questions should be directed to the list owner/operator: david@midrange.com
+---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.