Re: PERFORM composite joins?
Ahhh... The pitfalls of PERFORM. As far as I know you can't do this with PERFORM. What is it you're trying to do? If you want to display tableR data for reference, I suggest using the lookup attribute (If descriptions are needed to be displayed for items, etc..). If you're trying to join tables for detail row updating, you can't do it this way. You will need to use ESQL/C with PERFORM to accomplish this or move move your application to 4GL. Nick Leporacci, Jr. Jim Kistler wrote in message <6c1lfb$6ar@hpaneqb4.an.hp.com>... >I want to use four composite joins in a single form (PERFORM form builder) >where each composite join matches a DIFFERENT table (table1) column pair to >a SINGLE column pair in a reference table (tableR). > >e.g. > >attributes: >------------ >001 = table1.col_1; > = tableR.col_1; > >002 = table1.col_2; > = tableR.col_2; >----------------------- >003 = table1.col_3; > = tableR.col_1; > >004 = table1.col_4; > = tableR.col_2; >----------------------- >005 = table1.col_5; > = tableR.col_1; > >006 = table1.col_6; > = tableR.col_2; >----------------------- >007 = table1.col_7; > = tableR.col_1; > >008 = table1.col_8; > = tableR.col_2; >----------------------- > >instructions: >------------- > >composites <table1.col_1,table1.col_2> > <tableR.col_1,tableR.col_2> > >composites <table1.col_3,table1.col_4> > <tableR.col_1,tableR.col_2> > >composites <table1.col_5,table1.col_6> > <tableR.col_1,tableR.col_2> > >composites <table1.col_7,table1.col_8> > <tableR.col_1,tableR.col_2> > >Plus my reference table "tableR" also provides a third column that I use to >check that the composite "values" are present in that table. >---------------------------------------------------------------------- >PROBLEM....the PERFORM compiler complains that I should not >be setting the SAME joined columns from tableR to DIFFERENT columns in >table1. > ># ># The column "col_1" name appears more than once. If you ># wish a column to be duplicated in a form, use the same display field label. ># See error number -2892. > > >I can only make this work if I create FOUR reference tables all with the >SAME data...but this seems to be a waste! > >Any and all advice appreciated! > >Thanks, > >Jim >-- >=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=#=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= -=- > Jim Kistler - kistler@an.hp.com # Some see issues and ask, "Why? > Hewlett-Packard Co. Imaging Systems # Others see opportunities and > 3000 Minuteman Road, Andover, MA 01810 # ask, "Why not?" > TEL: 978-659-2251 - FAX: 978-687-7265 # >=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=#=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= -=-