|
If TrustedLink will let Greg do that, of course. I think I covered that in
a reply - there is a DFT in DDS, and the docs suggest it will use current
date or time, if you don't specify it - I think you also should not specify
a field in the WRITE.
SQL is the ticket here, of course, as you say.
Cheers
Vern
On Thu, 10 Aug, 2023 at 2:37 PM, Rob Berendt <robertowenberendt@xxxxxxxxx>
wrote:
To: midrange systems technical discussion
Here's the problem: "... an existing database file (DDS)".
Quit that. Use SQL's DDL instead. DDL will allow you to default new
columns to current date, etc. DDS will NOT. Sure, you can add triggers
and stuff but that isn't really DDS, is it?
On Thu, Aug 10, 2023 at 1:57 PM Greg Wilburn <
gwilburn@xxxxxxxxxxxxxxxxxxxxxxx<mailto:gwilburn@xxxxxxxxxxxxxxxxxxxxxxx>>
wrote:
I recently added an ISO date and ISO time field to an existing databasewe
file (DDS). This file is populated by our TrustedLink EDI software when
receive an inbound PO. I guess I had hoped it would capture thedate/time
the record was created. Tli support says the EDI translator won't updatehttps://www.totalbizfulfillment.com/>> Greg Wilburn
those "automatically".
Anyone know of a method of getting these fields to update with current
info upon creation? Otherwise, I'll have to update them in my RPG
processing program.
TIA,
Greg
[Logo]<https://www.totalbizfulfillment.com/><
Director of ITgwilburn@xxxxxxxxxxxxxxxxxxxxxxx>>
301.895.3792 ext. 1231
301.895.3895 direct
gwilburn@xxxxxxxxxxxxxxxxxxxxxxx<mailto:gwilburn@xxxxxxxxxxxxxxxxxxxxxxx
<mailto:gwilburn@xxxxxxxxxxxxxxxxxxxxxxx<mailto:
1 Corporate Drhttp://www.totalbizfulfillment.com<http://www.totalbizfulfillment.com>>
Grantsville, MD 21536
www.totalbizfulfillment.com<http://www.totalbizfulfillment.com><
--list
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx<mailto:MIDRANGE-L@xxxxxxxxxxxxxxxxxx>
To subscribe, unsubscribe, or change list options,MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx>
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx<mailto:
Before posting, please take a moment to review the archivessupport@xxxxxxxxxxxxxxxxxxxx> for any subscription related
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx<mailto:
questions.--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx<mailto:
MIDRANGE-L@xxxxxxxxxxxxxxxxxx>
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx<mailto:
MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx>
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx<mailto:
support@xxxxxxxxxxxxxxxxxxxx> for any subscription related questions.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
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.