You cannot add a Wrk table to any other report. In many cases it does not actually exist and in all cases it is empty of date until the printing program it references is run. In this case Invoice Printing. You need to add the CI table instead

That would explain why I was so frustrated. Do I need to do anything other than add the field? Is there a formula that I need to create? Thanks, BigLouie.

You have to first link in the CI_Item table and then the CI_ExtendedDescription table. Link the two CI tables based on the extended description key.

The result of simply adding the CI_ExtendedDescription table to the report database, then dragging the field ExtendedDescriptionText to the report: I ended up with an 1145-page report, with the first 1144 pages filled with the bill number and description, with the components tacked to the very end. When I added the CI_Item table as well, and linked them by name, I got 2878 pages, no bill number or description, and each component was listed multiple times with what appears to be every extended description in the database. I haven't decided whether that's progress...

OK let me be a little more specific. In the BM_GrossRequirementsWrk table create a UDF and make it a Business Object and then as source select CI_Item and then Extended Description Key. Update the ODBC. Next open the report in Design view and add the CI_extendeddescription table and link on the key as a left outer since not all the items would have extended description. Update the ODBC and then open the report in design mode and do an Update Database. Then add the field to the report.

Specificity is good, as I'm approaching this from a complete lack of programming knowledge/experience. And most of what I've managed to do so far can be attributed to luckily stumbling upon the answer. I'm going to need help from the IT department on the ODBC, as I don't want to do something that makes a huge mess.

Specificity is good, as I'm approaching this from a complete lack of programming knowledge/experience. And most of what I've managed to do so far can be attributed to luckily stumbling upon the answer. I'm going to need help from the IT department on the ODBC, as I don't want to do something that makes a huge mess.

OK you don't understand. In Custom Office when you create a UDF there is a prompt to update the ODBC settings. It happens in Custom Office. I would suggest working with your reseller if this is your first time with UDFs