× 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.



Simplest way architecturally is as follows:

1. Do SELECT including bad field
2. Check SQLCOD
3. On error, do SELECT excluding bad field and then initialize it

From a coding standpoint it's not too terrible, but since you're doing SELECT * it gets a bit more difficult.  Also, as you have more fields it gets quite a bit trickier.  But that's the best I've been able to come up with. Basically, as long as you have bad data, SQL is going to be difficult.



On 2/20/2019 2:55 PM, Jay Vaughn wrote:
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.

Example

Embedded sql...

select * from table into :ds_table


BUT I'm wanting to try and have SQL detect and handle the data during
processing so that processing is not interrupted.

If anyone has any experience with this issue and wish to share the
resolution I'd appreciate it.

Jay



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.