looking up data from one table and putting it into another table

Wayne Contello Austin, Texas
Cathy,
=SUMIF(I2:I92,GirlOrderReport :: L2:L72,GirlOrderReport :: AC2:AC72)
should be:
=SUMIF(I2:I72,...
I omitted the last part to highlight the typo. The size of the range MUST be the same so rows 2  72 are used for the conditions and should be the same size range for the sum.

Like (0)


The two different tables are two different lengths  the table that I am getting the data from has 71 rows with troop/girlgirl/troop transactions, while the table I am trying to get the data into has 91 rows  the 71 rows which correspond to the 71 rows in the other table plus the 20 rows that contain trooptroop/troopcouncil transactions.
The problem is that in the bigger table, all 71 of the common rows have the wrong value (zero), and I am trying to correct the values by looking them up in the smaller table, which has the right values.
Here's a screen shot of the two tables sidebyside that illustrates the data:
I'm trying to get the T2 column in the long table to say 142,142,141,1,1,etc... lokking up the data from the short table.

Like (0)


Wayne Contello Austin, Texas
Can you comment on whether the OrderID occurs more than once in either or both list? Also can you comment on whether, in the table on the left, the nonzero values correspond to COUNCIL and TROOP transactions (as opposed to GIRL).

Like (0)


OrderID is the primary key for each transaction, and that column is once in each table. The longer table
 has the orderID in column I
 In the "Total" column, each of the rows which shows a "Total" of zero is a GIRL transaction, and the correct total appears in the other (shorter) table, using the OrderID. Every nonzero value is a COUNCIL/TROOP transaction.
In the longer table, the GIRL row totals are all wrong but the COUNCIL/TROOP row totals are right. The shorter table only has GIRL rows, and all those rows are correct.
So the new column in the longer table is what I want to contain the correct number, which I want to fetch from the other table, using the OrderID as the field that needs to match up.

Like (0)


Wayne Contello Austin, Texas

Like (0)


Bingo!!!! (doing the happy dance... )
Thanks  I knew I kinda sorta had the idea...

Like (0)
