I've built my first database for a questionnaire, and there are 300 records
containing, among other things, filled fields named Q23 (text), Q24 (text)
and Q25 (text).  About half the records have blank values in these fields.
My goal is to print out the Q23 values, one after another, then the Q24
values, then Q25 values, omitting blank fields. This must be so simple.  Can
anyone help?

Thanks ==> Dick

-- 
****Email is dicksmith at charter dot net****

Thanks, this gets me going. But what prints is the entire record which
contains the non-empty Q23.  All I want is just Q23 by itself.  How to
suppress all the other stuff?  Also, only the first of the found records
prints, leaving the remaining found records unprinted.

Also, I'm unsure about the "Printsetup/Page setup" step, which I can't find.
Forgot to mention I'm running FP 4.0, Windows.

-- 
****Email is dicksmith at charter dot net****
"Hans Rijnbout" <j.b.rijnbout@chem.uu.nl> wrote in message
news:1fzoxf5.1f1gf9zikdjfyN%j.b.rijnbout@chem.uu.nl...
> Dick Smith <dicksmith.nospam@changethis.net> wrote:
>
> > My goal is to print out the Q23 values, one after another, then the Q24
> > values, then Q25 values, omitting blank fields. This must be so simple.
>
> Dick,
> It could be rather simple, but you need a separate print command for
> every field.
> Print setup/Page Setup [restore, no dialog]
> find records with Q23 not empty
> sort if necessary
> print [without dialog]
> find records with Q24 not empty
> sort if necessary
> print [without dialog]
> etc.
>
> Do the printing once by hand, exactly as you would have it, open the
> script in Scriptmaker, close the script and click 'replace print setup'
> in the keep/replace dialog. Often, but not always, this will store all
> relevant print parameters in your script.
> -- 
> Hans Rijnbout
> Utrecht, Netherlands

Dick Smith <dicksmith.nospam@changethis.net> wrote:

> Thanks, this gets me going. But what prints is the entire record which
> contains the non-empty Q23.  All I want is just Q23 by itself.  How to
> suppress all the other stuff?
  
Filemaker prints records using the current layout (see Filemaker Help
'Printing'). If you want to print only Q23 you should create a layout
that contains only this field. Empty fields can be made 'sliding' so
they don't take up space on the printed layout, you can see this effect
in Preview mode. 


> Also, only the first of the found records
> prints, leaving the remaining found records unprinted.

Did all found records print when you did the printing by hand? Did you
select 'records being browsed' in the print dialog? 
> 
> Also, I'm unsure about the "Printsetup/Page setup" step, which I can't find.
> Forgot to mention I'm running FP 4.0, Windows.
I'm not familiar with FMP4 under Windows. Maybe someone else can help
you there.


-- 
Hans Rijnbout
Utrecht, Netherlands

Hans, this is *very* helpful, and makes it work for me!  Thanks very much
for your assistance

==>Dick

-- 
****Email is dicksmith at charter dot net****
"Hans Rijnbout" <j.b.rijnbout@chem.uu.nl> wrote in message
news:1fzpbr8.5t2nxu1iqazg0N%j.b.rijnbout@chem.uu.nl...
> Dick Smith <dicksmith.nospam@changethis.net> wrote:
>
> > Thanks, this gets me going. But what prints is the entire record which
> > contains the non-empty Q23.  All I want is just Q23 by itself.  How to
> > suppress all the other stuff?
>
> Filemaker prints records using the current layout (see Filemaker Help
> 'Printing'). If you want to print only Q23 you should create a layout
> that contains only this field. Empty fields can be made 'sliding' so
> they don't take up space on the printed layout, you can see this effect
> in Preview mode.
>
>
> > Also, only the first of the found records
> > prints, leaving the remaining found records unprinted.
>
> Did all found records print when you did the printing by hand? Did you
> select 'records being browsed' in the print dialog?
> >
> > Also, I'm unsure about the "Printsetup/Page setup" step, which I can't
find.
> > Forgot to mention I'm running FP 4.0, Windows.
> I'm not familiar with FMP4 under Windows. Maybe someone else can help
> you there.
>
>
> -- 
> Hans Rijnbout
> Utrecht, Netherlands

Bridget,

Your post is just the kind of transparent invitation that makes me want to
do this thing all over again, this time the right way. I *knew* there was a
relational way to think about it, but I just couldn't get to it. Your note
really helps.  I wonder how long it'll take for me to fully understand it.
Thanks very much.

-- 
****Email is dicksmith at charter dot net****
"Bridget Eley" <bridgeteley@ihug.com.au> wrote in message
news:BB623FBF.294A%bridgeteley@ihug.com.au...
> Hi Dick
>
> I am not sure if this will help with your current problem but for future
> questionnaires, consider using a many to many file structure, that is two
> parent files joined by a common child file.  Why? Because a participant
can
> answer many questions and each question can be answered by many
> participants. Whenever you can say this about a pair of database entities,
a
> many to many file structure is usually the most robust solution.
>
> One of the parents is the Participant file. Each record in Participants
> contains the details of one participant.  The other parent is the
Questions
> file.  Each record in Questions contains details of one question, that is,
> question number and question.  Each records in the join file carries the
> response of one participant to one question.  A portal is set up in the
> participant file that displays records from the join file  via a
> relationship based on Participant ID.  A scripted button can be created
that
> automatically creates a new participant record and at the same time a
record
> in the join file for each question (linked to Participant by Participant
ID
> and to Questions by Question Number).  The join file should also include a
> calc field that pulls the actual question from the question file using a
> relationship based on Question Number (= relationship::question).  So, you
> click the button and a new Participant record is made and the portal fills
> up with records showing question number, question calc, and response text
> field. The participant  (or the date entry person) inputs their responses
> in the portal.
>
> Because each child record contains the answer to only one question by one
> participant, printing is a breeze, just perform a find which omits records
> without an entry in the response field, sort by question number and print.
>
> This approach will also allow you to summarise data in various ways and to
> produce all kinds of useful and professional looking reports in the join
> file.
>
> If you are interested but need more help with this, please post again.
>
> Bridget Eley
>
>
>
>
> in article vjn7j92sbpdg51@corp.supernews.com, Dick Smith at
> dicksmith.nospam@changethis.net wrote on 15/8/03 12:35 AM:
>
> > I've built my first database for a questionnaire, and there are 300
records
> > containing, among other things, filled fields named Q23 (text), Q24
(text)
> > and Q25 (text).  About half the records have blank values in these
fields.
> > My goal is to print out the Q23 values, one after another, then the Q24
> > values, then Q25 values, omitting blank fields. This must be so simple.
Can
> > anyone help?
> >
> > Thanks ==> Dick
>

Its not that hard, although not without limitations.  It works best with all
plain text answers OR all multiple choice with exactly the same no of
possible responses for every questions AND either check box or radio button
responses for all questions.  Mixed responses (some plain text, some check
box, some radio button, and different numbers of possible responses, etc)
can be problematic - although there are work- arounds.  Email if you want to
see a rough demo, including a demo report with bar graph.

Bridget Eley

in article vjobk8qn8mlecd@corp.supernews.com, Dick Smith at
dicksmith.nospam@changethis.net wrote on 15/8/03 10:50 AM:

> Bridget,
> 
> Your post is just the kind of transparent invitation that makes me want to
> do this thing all over again, this time the right way. I *knew* there was a
> relational way to think about it, but I just couldn't get to it. Your note
> really helps.  I wonder how long it'll take for me to fully understand it.
> Thanks very much.