New Request - I don't know why it is tricky 
Author Message
 New Request - I don't know why it is tricky

Hi again,
    I have two files: Paddocks.FP5 and Rows.FP5.  The obviously relation
holds that each paddock has X no of rows - related to that paddock.  The
layout for Paddock shows X fields representing X number of rows.  Entry to
the rows is random - not sequential (therefore a portal is out of the
question).  Information entered is number of fruit-picked in any particular
row on a particular day (with each record in Paddock representing a new
day).  Perhaps it is wrong of me, but what I would like to be able to do is
click on a row field in paddock and enter the 'value'.  However, I truly
want this value to be an entry in Rows.FP5.  Naturally, this works simply on
a one-to-one relationship if only one row was related to only one paddock.
This of course is not the case.  Many rows relate to one paddock.
    My question - is how can a click in any 'related-row' field on the
paddock file say row 1,5, and 7 - of 10 rows in total - and have three
related records created in the Rows.FP5.  When ever I try, as soon as I
enter a value into say row 5 - rows 1 through 10 automatically adopt that
value - naturally, due to the matching.  But all my attempts to overcome
this result in 'circular' argument errors.

Help is appreciated.
Jason



Mon, 10 Nov 2003 09:49:30 GMT
 New Request - I don't know why it is tricky

Quote:

> Hi again,
>     I have two files: Paddocks.FP5 and Rows.FP5.  The obviously relation
> holds that each paddock has X no of rows - related to that paddock.  The
> layout for Paddock shows X fields representing X number of rows.  Entry to
> the rows is random - not sequential (therefore a portal is out of the
> question).  Information entered is number of fruit-picked in any particular
> row on a particular day (with each record in Paddock representing a new
> day).  Perhaps it is wrong of me, but what I would like to be able to do is
> click on a row field in paddock and enter the 'value'.  However, I truly
> want this value to be an entry in Rows.FP5.  Naturally, this works simply on
> a one-to-one relationship if only one row was related to only one paddock.
> This of course is not the case.  Many rows relate to one paddock.
>     My question - is how can a click in any 'related-row' field on the
> paddock file say row 1,5, and 7 - of 10 rows in total - and have three
> related records created in the Rows.FP5.  When ever I try, as soon as I
> enter a value into say row 5 - rows 1 through 10 automatically adopt that
> value - naturally, due to the matching.  But all my attempts to overcome
> this result in 'circular' argument errors.

> Help is appreciated.
> Jason

It's your data structure that's the problem. You've basically got three
entities, not two. Paddocks, Rows, and Days.

Paddocks
In this file should be one record for each Paddock, with a Paddock ID.

Rows
In this file is one record per row in each paddock. Each record has a
Paddock ID, and a Row ID.

PickingDays is essentially a join file between days and Rows..there is
one record per row per day picked. (in this case, we really don't need a
Days file to pull values from, dates can just be entered with the other
data). Each record here has both a Paddock ID and a RowID, as well as a
date.

Now, you can put portals in Paddocks to show all the Rows belonging to
that Paddock. You can put a portal in Rows showing all the picking day
data for each row. You will be able to (with some thought) script
entries into PickingDays from the Paddock file itself, if you want to,
or more simply, from the Rows file.

Get your relationships straight, and all else will follow. :)

--
Lynn Allen              Allen & Allen Semiotics
FSA Associate           Filemaker Consulting & Training



Tue, 11 Nov 2003 09:38:23 GMT
 New Request - I don't know why it is tricky
Hi again Jason -

Sorry , I posted in your earlier thread before seeing this one.  My questions
about record definition and relational structure were leading to exactly what Lynn
has shown you in her suggestion.  Please disregard the other thread, and if you
have more questions about these concepts get back to the group.

Best of Luck -
James

Quote:


> > Hi again,
> >     I have two files: Paddocks.FP5 and Rows.FP5.  The obviously relation
> > holds that each paddock has X no of rows - related to that paddock.  The
> > layout for Paddock shows X fields representing X number of rows.  Entry to
> > the rows is random - not sequential (therefore a portal is out of the
> > question).  Information entered is number of fruit-picked in any particular
> > row on a particular day (with each record in Paddock representing a new
> > day).  Perhaps it is wrong of me, but what I would like to be able to do is
> > click on a row field in paddock and enter the 'value'.  However, I truly
> > want this value to be an entry in Rows.FP5.  Naturally, this works simply on
> > a one-to-one relationship if only one row was related to only one paddock.
> > This of course is not the case.  Many rows relate to one paddock.
> >     My question - is how can a click in any 'related-row' field on the
> > paddock file say row 1,5, and 7 - of 10 rows in total - and have three
> > related records created in the Rows.FP5.  When ever I try, as soon as I
> > enter a value into say row 5 - rows 1 through 10 automatically adopt that
> > value - naturally, due to the matching.  But all my attempts to overcome
> > this result in 'circular' argument errors.

> > Help is appreciated.
> > Jason

> It's your data structure that's the problem. You've basically got three
> entities, not two. Paddocks, Rows, and Days.

> Paddocks
> In this file should be one record for each Paddock, with a Paddock ID.

> Rows
> In this file is one record per row in each paddock. Each record has a
> Paddock ID, and a Row ID.

> PickingDays is essentially a join file between days and Rows..there is
> one record per row per day picked. (in this case, we really don't need a
> Days file to pull values from, dates can just be entered with the other
> data). Each record here has both a Paddock ID and a RowID, as well as a
> date.

> Now, you can put portals in Paddocks to show all the Rows belonging to
> that Paddock. You can put a portal in Rows showing all the picking day
> data for each row. You will be able to (with some thought) script
> entries into PickingDays from the Paddock file itself, if you want to,
> or more simply, from the Rows file.

> Get your relationships straight, and all else will follow. :)

> --
> Lynn Allen              Allen & Allen Semiotics
> FSA Associate           Filemaker Consulting & Training


--
Don't forget to remove the obvious spam block when replying.
I advocate making an address book entry and using it!  Thanks!


Tue, 11 Nov 2003 16:46:50 GMT
 New Request - I don't know why it is tricky
I think that you use, in rows file, the field of poddocks file. It's wrong.
If you want enter a value in a specific rows, the rows file must be a field
owner.

Diego

Quote:

> Hi again,
>     I have two files: Paddocks.FP5 and Rows.FP5.  The obviously relation
> holds that each paddock has X no of rows - related to that paddock.  The
> layout for Paddock shows X fields representing X number of rows.  Entry to
> the rows is random - not sequential (therefore a portal is out of the
> question).  Information entered is number of fruit-picked in any particular
> row on a particular day (with each record in Paddock representing a new
> day).  Perhaps it is wrong of me, but what I would like to be able to do is
> click on a row field in paddock and enter the 'value'.  However, I truly
> want this value to be an entry in Rows.FP5.  Naturally, this works simply on
> a one-to-one relationship if only one row was related to only one paddock.
> This of course is not the case.  Many rows relate to one paddock.
>     My question - is how can a click in any 'related-row' field on the
> paddock file say row 1,5, and 7 - of 10 rows in total - and have three
> related records created in the Rows.FP5.  When ever I try, as soon as I
> enter a value into say row 5 - rows 1 through 10 automatically adopt that
> value - naturally, due to the matching.  But all my attempts to overcome
> this result in 'circular' argument errors.

> Help is appreciated.
> Jason



Tue, 11 Nov 2003 17:18:34 GMT
 New Request - I don't know why it is tricky
Thanks Lynn (and thank you to James),
    One of my biggest issues - is to stop and see the relationships - before
I try to build the relationships.  I get mixed up with identifying the
enitity - over the (small stuff or attributes).  Plus, I always want to
multi-use all my files with other files... bigger dreams

Thank you...

Quote:

> > Hi again,
> >     I have two files: Paddocks.FP5 and Rows.FP5.  The obviously relation
> > holds that each paddock has X no of rows - related to that paddock.  The
> > layout for Paddock shows X fields representing X number of rows.  Entry
to
> > the rows is random - not sequential (therefore a portal is out of the
> > question).  Information entered is number of fruit-picked in any
particular
> > row on a particular day (with each record in Paddock representing a new
> > day).  Perhaps it is wrong of me, but what I would like to be able to do
is
> > click on a row field in paddock and enter the 'value'.  However, I truly
> > want this value to be an entry in Rows.FP5.  Naturally, this works
simply on
> > a one-to-one relationship if only one row was related to only one
paddock.
> > This of course is not the case.  Many rows relate to one paddock.
> >     My question - is how can a click in any 'related-row' field on the
> > paddock file say row 1,5, and 7 - of 10 rows in total - and have three
> > related records created in the Rows.FP5.  When ever I try, as soon as I
> > enter a value into say row 5 - rows 1 through 10 automatically adopt
that
> > value - naturally, due to the matching.  But all my attempts to overcome
> > this result in 'circular' argument errors.

> > Help is appreciated.
> > Jason

> It's your data structure that's the problem. You've basically got three
> entities, not two. Paddocks, Rows, and Days.

> Paddocks
> In this file should be one record for each Paddock, with a Paddock ID.

> Rows
> In this file is one record per row in each paddock. Each record has a
> Paddock ID, and a Row ID.

> PickingDays is essentially a join file between days and Rows..there is
> one record per row per day picked. (in this case, we really don't need a
> Days file to pull values from, dates can just be entered with the other
> data). Each record here has both a Paddock ID and a RowID, as well as a
> date.

> Now, you can put portals in Paddocks to show all the Rows belonging to
> that Paddock. You can put a portal in Rows showing all the picking day
> data for each row. You will be able to (with some thought) script
> entries into PickingDays from the Paddock file itself, if you want to,
> or more simply, from the Rows file.

> Get your relationships straight, and all else will follow. :)

> --
> Lynn Allen              Allen & Allen Semiotics
> FSA Associate           Filemaker Consulting & Training




Fri, 14 Nov 2003 16:02:11 GMT
 
 [ 5 post ] 

 Relevant Pages 

1. Oninit didn't work fine and I don't know why

2. SQL server name has been changed and don't know why

3. I don't know why, do you????????????????/

4. Database properties settings changed back to default settings and I don't know why

5. ADO Error! Don't know why

6. Subroutine not cataloged error, and I don't know why

7. Page fault and don't know why

8. About Foxpro (Don't know why?)

9. Don't know the field name but do know the column order

10. why oh why don't labels ever work

11. I've just replaced the last dBA and don't know the sa password

12. Funny Behaving Locate - don't know where's the problem


 
Powered by phpBB® Forum Software