Ah, you mean "do it the way you've been doing all your other reports for the past 5 years". But that makes too much sense....
On Sat, Aug 25, 2012 at 5:10 PM, Fred Taylor <fbtay...@gmail.com> wrote: > Why screw with the relations? Use SQL to gather everything you need into a > single cursor for reporting. Much easier to debug as you can see what's > happening. > > Fred > > > On Sat, Aug 25, 2012 at 2:01 PM, Garrett Fitzgerald < > sarekofvul...@gmail.com > > wrote: > > > It's been too long since I tried to get cute with reports. I just > created a > > form for a wedding registry which would fire off a report at the end > > listing the items. To do this, I related the RegistryHdr to the > RegistryDet > > to the Catalog to the Dept tables. I then selected the Detail table and > > fired off the report with REPORT FORM registry PREVIEW FOR > > RegistryDet.iRegistryID = liRegistryID. That gives me the detail lines I > > need, but no header information or department information. If I drop the > > FOR clause, it works fine. What am I missing here? > > > > Thanks. > > > > > > --- StripMime Report -- processed MIME parts --- > > multipart/alternative > > text/plain (text body -- kept) > > text/html > > --- > > [excessive quoting removed by server] _______________________________________________ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/CAGd8MrcEM7sFUrguFNRSyBBv9OdbLMfw9Nr4Pf92FFoAU1f=w...@mail.gmail.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
