home *** CD-ROM | disk | FTP | other *** search
- Nntp-Posting-Host: bert.cs.byu.edu
- Lines: 34
- Path: sparky!uunet!news.mtholyoke.edu!news.byu.edu!news
- Message-ID: <s1#@byu.edu>
- Date: Wed, 27 Jan 93 17:08:12 MST
- From: ron@bert.cs.byu.edu (Ron Snyder)
- Organization: BYU Computer Science
- Newsgroups: comp.databases
- Subject: Re: Paradox question
- References: <mcdonald.693.727814490@aries.scs.uiuc.edu>
- <1993Jan24.144529.19009@nuscc.nus.sg>
- <1993Jan27.110322.1326@actrix.gen.nz>
- <1993Jan27.090537.17710@hellgate.utah.edu>
-
- >it. Use this second table to design reports, forms etc. Every time
- >you do a query and want to use one of the reports or forms, do a F10
- >Tools Copy Justfamily "skeleton" "Answer".
- ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
- I believe "Copy" overwrites the table and could hose your reports....it
- is safer to empty "skeleton", add "answer" "skeleton" from a script ...
- that way you know exactly what is in the skeleton table at all times.
-
- When you Copy JustFamily, it leaves the destination table (in this
- case, the answer table) alone, and just replaces any forms and reports
- that existed for the answer table. As to your other advice, in general
- is a better idea to not empty "skeleton" and then add "answer" "skeleton",
- because of the time involved in this procedure, especially when there is
- a large amount of data that would have to be moved. I have seen
- several suggestions from the 'experts' to do a
-
- copyreport "skeleton" "1" "answer" "1"
- report "answer" "1"
-
- when this will do what is needed. (Of course, you would have to pick
- your own table names and report numbers.) The advantage that this
- method has over doing a "Copy JustFamily" is that if "skeleton" has
- a lot of reports and forms, then that extra baggage stays where it
- is, and you only copy the report that you want.
-
-
-
-
-
-
- --
- Ron Snyder <ron@bert.cs.byu.edu> <snyderrj@coned1.byu.edu>
- ****************************************************************
-