Re: Base - relationships

jomali <[email protected]>
Newsgroups gmane.comp.openoffice.dba.user
Message-ID <[email protected]>
I duplicated your example, and it worked correctly. I entered a date, then
clicked in the visits area, and the date ID incremented to the next value
and that value was entered into the FKDate field of the first address
record. Since I can't duplicate your problem, I cannot help you.

John

On Wed, Sep 9, 2009 at 6:56 PM, FamiliaFrazelle <[email protected]>wrote:

> Irné Barnard wrote:
>
>> Depends on how you want to input / display the data. Search (e.g. google)
>> for Entity-Relationship diagram techniques. It's the method of graphically
>> mapping & designing the database. E.g. Would a visit only happen once to any
>> one house? In this case the house's street number could form part of the
>> Visits table.
>> Regards Irné Barnard
>>
>>
>> FamiliaFrazelle wrote:
>>
>>> i hope this is the correct forum for this...
>>>
>>>  i'm still trying to get this to work...
>>>
>>>  i've created two tables: Dates and Visits.  This is a bare-bones setup
>>> to see if it works.  The idea is to input info from visits to homes into the
>>> Visits table.  Since many visits to homes are made on the same day, it would
>>> seem reasonable to NOT include the visit date in the Visits table, but make
>>> a separate table for it and relate it to the Visits table in a one-to-many
>>> relationship.
>>>  If i can get this to work, it would also seem reasonable to remove the
>>> Neighborhood name and the Street name from the Visits table and place them
>>> in separate, individual tables as well, since they are repeated values in
>>> the Visits table (many addresses on the same street and many addresses in
>>> the same neighborhood).
>>>
>>>  So, i created the following:
>>>
>>> Dates table
>>> IDDates, Primary, Integer, Autoincrement
>>> Dates, DateType
>>>
>>> Visits table
>>> IDVisits, Primary, Integer, Autoincrement
>>> Street, Text
>>> FKDate, Integer, Input not Required
>>>
>>>  My questions are these:
>>>
>>>  Are these sufficient fields? If so, how should i Relate them in the
>>> Relationships window so that when i input a new date in the Dates Table the
>>> corresponding Foreign Key in the Visits Table will automatically receive a
>>> new value?
>>>
>>>  i've created these tables and the relationship in Tools, Relationship,
>>> and then tried to create a form but when i got to input info through the
>>> form, i can input the first date and the FKDate control appears as 0 (zero)
>>> which is correct and corresponds to the first IDDates value.  Then, i can
>>> continue to input new records alright.  But, when i try to input another
>>> date, the control will accept it, but when i change to the Visits area, the
>>> FKDate field doesn't increment to a new value, it remains zero.  What am i
>>> not doing correctly?  Or is Base not capable of this type of input?
>>>
>>> Have a great afternoon! :)
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>>
>>  Thank you Irné for replying.  i was afraid that this would happen if i
> asked too many questions.  The only part i'm interested in/having
> difficulties with at this point i the last part...
>
>  " i've created these tables and the relationship in Tools, Relationship,
> and then tried to create a form but when i got to input info through the
> form, i can input the first date and the FKDate control appears as 0 (zero)
> which is correct and corresponds to the first IDDates value.  Then, i can
> continue to input new records alright.  But, when i try to input another
> date, the control will accept it, but when i change to the Visits area, the
> FKDate field doesn't increment to a new value, it remains zero.  What am i
> not doing correctly?  Or is Base not capable of this type of input? "
>
>   Have a great afternoon!  :)
>
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.