Re: SQL and invalid data in field

Put a trigger on the file and check the date field in the trigger program
and log the program that inserted the incorrect date.

Or put a journal on the file and interrogate the journal to find the
program(s) that are putting invalid data in the file.

This is not a time consuming exercise.

And fixing the problem is far better than continually fixing the data.

My 2cents


Don Brown

"MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> wrote on 21/02/2019
07:32:21 AM:

From: "Jay Vaughn" <jeffersonvaughn@xxxxxxxxx>
To: "Midrange Systems Technical Discussion"

<midrange-l@xxxxxxxxxxxxxxxxxx>

Date: 21/02/2019 07:32 AM
Subject: Re: SQL and invalid data in field
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxxxxxxxx>

sorry dave - no, it is the class 8p0 date field

On Wed, Feb 20, 2019 at 4:06 PM <dlclark@xxxxxxxxxxxxxxxx> wrote:

"MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> wrote on

02/20/2019

03:55:14 PM:

So occasionally we come across data in our files that SQL does not

like

to

play with.
RLA handles it fine. But as we move more towards SQL it is becoming

a

problem.

You say the column is called COLI_CHANGE_DATE. Is the column

data

type actually DATE? You didn't say, but what is the actual data in

the

column when it errors out? The answer to these questions will

determine

the course of action.


Sincerely,

Dave Clark
--
int.ext: 91078
direct: (937) 531-6378
home: (937) 751-3300

Winsupply Group Services
3110 Kettering Boulevard
Dayton, Ohio 45439 USA
(937) 294-5331

*********************************************************************************************

This email message and any attachments is for use only by the named
addressee(s) and may contain confidential, privileged and/or

proprietary

information. If you have received this message in error, please
immediately notify the sender and delete and destroy the message and

all

copies. All unauthorized direct or indirect use or disclosure of this
message is strictly prohibited. No right to confidentiality or

privilege

is waived or lost by any error in transmission.

*********************************************************************************************

--
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@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com

--
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@xxxxxxxxxxxx for any subscription related

questions.

Help support midrange.com by shopping at amazon.com with our affiliate

link:

https://amazon.midrange.com

______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud

service.

For more information please visit http://www.symanteccloud.com
______________________________________________________________________

______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________