>>>The general flow of the report is like this:
>>>+------------ provider id (break)
>>>|
>>>| +------Address id (break)
>>>| | +---TaxId
>>>| | | (detail)
>>>| | +---
>>>| +------
>>>|
>>>| +-----TaxId WHERE EMPTY( dm_AddrId)
>>>| | (detail)
>>>| +-----
>>>|
>>>| +-----Spec_code
>>>| | (detail)
>>>| +-----
>>>|
>>>| +-----State_lic
>>>| | (detail)
>>>| +-----
>>>|
>>>+------------
>>>
>>>I'm just gettin' warmed up. Wanna know more... :)
>>>
>>> ...kt
>>
>>So far, i don't see problems. You collect one-many tables to one cursor with >ProviderID,AddressID,TaxID ... Now you can just order this cursor by this 3 >fields providing that empty AddressID will go last.
>
>Two problems with this approach. 1) I think that after I get the final address break the detail lines will print all of the TaxId's under one blank address, correct? I need to print each TaxId as if it has a seperate address. 2) for brevity sake (well, I did try anyway) I didn't detail the other parts of the report. It also has to print provider specialty codes and state licenses in a seperate section/format. Using your approach would associate specialties and licenes with a particular address, not with at the provider level. In other words the specialties and licenses would print each time an address prints.

Hey Keith,
Ed has you on the right track... I have a reporting sytem with over 200 reports and I've beat myself up with scenarios like this but always managed to make them work with regular Report Writer. Rule on Thumb on your latest question - Whenever you think you need "a separate section" you can usually put fields in Header/Footer Band to make it work. So for this, I'd put Provider codes and state lincense info in the header for your Provider group. =D) What's next?