home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.databases
- Path: sparky!uunet!dcatlas!joet
- From: joet@dcatlas.dot.gov (Joe Trott)
- Subject: Re: Paradox 4.0 form question...
- Message-ID: <1992Nov12.145700.10810@dcatlas.dot.gov>
- Organization: U.S Dept. of Transportation
- References: <92303.122721U15310@uicvm.uic.edu> <1992Nov5.130812.1@skcla.monsanto.com>
- Date: Thu, 12 Nov 1992 14:57:00 GMT
- Lines: 18
-
-
- >In article <92303.122721U15310@uicvm.uic.edu>, <U15310@uicvm.uic.edu> writes:
- >> In designing a Paradox form, I discover I can imbed a "child" table within
- >> a master form. But, I can't imbed (nest) a "child" table within the
- >> child form. In other words, I can't create a form that handles three
- >> levels of relationships. This seems like a serious limitation of the
- >> form designer. Any suggestions for a relatively easy way for getting
- >> around this limitation?
-
- You _can_, however, imbed two child tables in one master table. They can
- have the same or different linking fields. This may not be what you need
- (if you want a one-many-many it isn't), but it _is_ one way to link more than
- two tables on one form.
- You want nasty though? Now hard-code the report to output data from this
- structure, including the queries that generate it...
-
- -JTT
-
-