RE: Net.Data Variable names for join -- WEB400

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

Subject: RE: [WEB400] Net.Data Variable names for join
From: "Phil Groschwitz" <phil@xxxxxxxxxxxxxx>
Date: Sat, 23 Mar 2002 21:01:06 -0500
Importance: Normal
List-archive: <http://archive.midrange.com/web400/>
List-help: <mailto:web400-request@midrange.com?subject=help>
List-id: Web Enabling the AS400 / iSeries <web400.midrange.com>
List-post: <mailto:web400@midrange.com>
List-subscribe: <http://lists.midrange.com/cgi-bin/listinfo/web400>,<mailto:web400-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/cgi-bin/listinfo/web400>,<mailto:web400-request@midrange.com?subject=unsubscribe>

Peter,

Maybe you have to refer to it by position.  If b.person is the ninth column
in the table created by the join, then V_9.  Sounds familiar but not
positive.

A way around this is to select only the fields you need - not all of them.
That should avoid the ambiguity.

A great resource for net.data questions is IBM's net.data forum at
http://netdata.boulder.ibm.com/cgi-bin/db2www/forum.d2w/main and
ignite400.org.

Phil

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Net.Data Variable names for join , Peter Dow

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.