RE: .NET Managed Provider and Multi-member Files

That worked marvelously.

Thank you. 


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Scott A
Schollenberger
Sent: Tuesday, September 19, 2006 1:34 PM
To: Midrange Systems Technical Discussion
Subject: Re: .NET Managed Provider and Multi-member Files


Multi-member files is a foreign SQL concept.  You need to create an SQL
ALIAS for each member in the table and then
use the alias name instead of the table name.

lib/table1(member1) becomes lib/table1m1

The SQL ALIAS is created as a DDM file.
----------------------

Scott A. Schollenberger
Director, Research & Development
Harris Computer Systems
School division

2011 Renaissance Blvd., Suite 100
King of Prussia, PA  19406
Phone: 610-239-9988  Ext. 305
Fax: 610-239-9995
E-mail: saschollenberger@xxxxxxxxxxxx
              sschollenberger@xxxxxxxxxxxxxxxxxx
Web: www.tenexsys.com

IBM Certified Specialist - eServer i5 iSeries Technical Solutions
Implementer V5R3

CONFIDENTIALITY NOTICE:  This email message, including any attachments, is
for the sole use of the intended recipient(s) and contains confidential and
privileged information.  Any unauthorized review, use, disclosure or
distribution is prohibited.  If you are not the intended recipient, please
contact the sender by reply email and destroy all copies of the original
message.


                                                                           
             "Fisher, Don"                                                 
             <dfisher@roomstor                                             
             e.com>                                                     To 
             Sent by:                  <midrange-l@xxxxxxxxxxxx>           
             midrange-l-bounce                                          cc 
             s@xxxxxxxxxxxx                                                
                                                                   Subject 
                                       .NET Managed Provider and           
             09/19/2006 01:15          Multi-member Files                  
             PM                                                            
                                                                           
                                                                           
             Please respond to                                             
             Midrange Systems                                              
                 Technical                                                 
                Discussion                                                 
             <midrange-l@midra                                             
                 nge.com>                                                  
                                                                           
                                                                           




I am attempting to use the .NET managed provider in Visual Basic.NET to
retrieve data from a multi-member file.  I've been searching the
documentation and the archives without locating a way to do this.  Surely
there is some way to specify the member name containing the records to be
retrieved?

I've tried "library/filename(member)" and "library.filename(member)"
without success.  There is also apparently no way to specify the naming
convention to be used (SQL or System), but I guess that's a different
question.

If anyone has an idea how this can be done, I would greatly appreciate your
insight.  I have a workaround, but it's a bit ugly.

Donald R. Fisher, III
Project Manager
RoomStore, Inc.
(804) 784-7600 ext. 2124
dfisher@xxxxxxxxxxxxx

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