Path: utzoo!utgpu!water!watmath!clyde!bellcore!tness7!killer!osu-cis!tut.cis.ohio-state.edu!mandrill!gatech!ncar!oddjob!uwvax!umn-d-ub!umn-cs!mmm!ems!mpp From: mpp@ems.Ems.MN.ORG (Michael Palmquist) Newsgroups: comp.databases Subject: Paradox 2.0 Problem Keywords: query report Message-ID: <6333@ems.Ems.MN.ORG> Date: 2 Jun 88 16:01:35 GMT Organization: EMS/McGraw-Hill, Eden Prairie, MN Lines: 36 Posted: Thu Jun 2 11:01:35 1988 Hi -- Maybe this is a simple question for someone but it's a tricky thing for me. I'm using Paradox 2.0 (a product that's new to me) and am in the preliminary process of designing a corporate application that deals with financial, sales, and production specifications of publishing proposals -- lots of detail about a single product. This database will basicaly produce a lot of free-form reports that are used to get approval for the publishing project. They want to produce a free-form report from a table created by an "outer-join". There will be lots of records eventually, but users will print a "report" on only ONE of those records at a time. In SQL, selecting a single record from a table (record-type) and piping it to a report would be a piece of cake. In Paradox, I'm having trouble setting up an elegant method of selecting THE product to be sent to the "report". Do I need to use temporary tables? (i.e. Query the table, rename, and base the report on the renamed table) If so, what method can I use for record selection? I would like to use a Lookup Table or something like that. Any suggestions would be very helpful ... e-mail would be fine... ______________________________________________________________________________ There are three ways to ruin yourself: gambling, sex, and technology. Gambling is fastest, Sex the most pleasurable, And technology the most certain. -- Georges Pompidou, 1911-1974 mpp@ems.EMS.MN.ORG (Mike Palmquist) EMS/McGraw-Hill 9855 W. 78th St. Eden Praire, MN 55344 612/829-8200