Excellent catch, Mike! The CA* name was the original attempt, and from
where the error message was copied/pasted. The AR* name is the one I
settled on, but it still gave the same error.

So, while Rob's suggestion resolved the issue for me, the problem with the
error associated with the UNION clause appears to be a defect.

Thanks,
- Dan

On Thu, Feb 8, 2018 at 12:45 PM, Mike Jones <mike.jones.sysdev@xxxxxxxxx>
wrote:

Hi Dan,

I notice that in the error message, it states table name "CA0119W".

In your SQL, it builds table name "AR0119W", a different name.

<snip>

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.