× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MIDRANGE-L
  3. November 2007

RE: How is it possible to have invalid time in a time field?

Have you seen Infinium's Hundred Year Format Dates?

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Paul Nelson
Sent: Friday, November 02, 2007 11:44 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: How is it possible to have invalid time in a time field?

I've seen those also. Then there's JDE with their Julian dates.

Speaking of JDE, do any of you know of instances where companies who
have
tried and failed to make the jump to Oracle are now moving to JDE
(mostly
because Oracle owns JDE and won't have to return a lot of money)?

I've got a client who is considering just such a move, never mind the
fact
that JDE is not a good fit for their industry.

Paul Nelson
Cell 708-670-6978
Office 512-392-2577
nelsonp@xxxxxxxxxxxxx


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Mark Allen
Sent: Friday, November 02, 2007 10:37 AM
To: Midrange Systems Technical Discussion
Subject: Re: How is it possible to have invalid time in a time field?

beats CYYMMDD where C is 0 for 1900 and 1 for 2000

On 11/2/07, Paul Nelson <nelsonp@xxxxxxxxxxxxx> wrote:

Heh. I know a package that throws garbage into its files when
calculating
due dates. If the invoice date is 9/1/07 and the terms are 30 days,
one
ends
up with 9/31/07 as the due date.

The vendor's response? Yeah, we know, but we code around it in our
other
programs. Unfortunately, they store dates as YYYYMMDD.

Paul Nelson
Cell 708-670-6978
Office 512-392-2577
nelsonp@xxxxxxxxxxxxx


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Friday, November 02, 2007 10:21 AM
To: Midrange Systems Technical Discussion
Subject: Re: How is it possible to have invalid time in a time field?

Tommy,

What you said holds some water, but when it is all said and done, you
still need the Fort Knox of data validation. I've discovered that
many
packages do fine validation. It's the programmers out at the customer
who
are most likely to hose up the data. They are the ones who do data
conversions, interface data from other batch processes, such as EDI or
barcoding. Merging of databases, uploading from Excel, etc.

For example one package uses no primary key. And on their DDS for
their
logical they specify no UNIQUE key. If you use their program logic
then
the odds are slim to none that you will ever have duplicate keys.
However
in the process of merging databases and/or conversions we do. And
that's
in the item master. All this could have easily been stopped at the
moat
by a primary key constraint.

Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





Tommy.Holden@xxxxxxxxxxxxxxxxxxxxx
Sent by: midrange-l-bounces@xxxxxxxxxxxx
11/02/2007 10:56 AM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
cc

Fax to

Subject
Re: How is it possible to have invalid time in a time field?






even DDS files shouldn't have crap in them...that's why you should
validate data prior to writing data out! be that as it may
unfortunately
lots of stuff out there do not do validation (which i would still
validate

even with SQL tables). in this day and age every programmer should
know
to validate prior to write/update. too bad some 3rd party vendors
STILL
don't do proper validation....

Thanks,
Tommy Holden



rob@xxxxxxxxx
Sent by: midrange-l-bounces@xxxxxxxxxxxx
11/02/2007 09:39 AM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
cc

Subject
Re: How is it possible to have invalid time in a time field?






It's easy. You defined your fields with DDS right? You can put all
sorts


of (expletive deleted) into files created with DDS. Files defined
with
SQL check at write time and will NOT let invalid data get into them.

Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





Booth Martin <booth@xxxxxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
11/02/2007 10:16 AM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
cc

Fax to

Subject
How is it possible to have invalid time in a time field?






I am getting a runtime halt that tells me that the value in a field is
invalid. The field is a time field. I do not understand how that is
possible. btw, the value that is invalid is '24.00.00' I understood
that by definition, date, time, and timestamp fields had to have valid
data. We can't have a data field of zeros, for example.

--
---------------------------------
Booth Martin
http://www.Martinvt.com
---------------------------------

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.




--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.



As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.