Hi Raven,
Regarding Frerquency, add another table to my original recommendation:
TblFrequency
FrequencyID
Frequency 'monthly, daily, etc.
Then add another field to TblReport:
FrequencyID
Add this relationship:
FrequencyID in TblFrequency ===> FrequencyID in TblReport
Create your relationships in the Relationships window. When creating
relationships, add the appropriate tables to the relationship window then
drag the primary key and drop it on the foreign. For example, n the above
relationship, TblFrequency and TblReport need to be in the relationship
window then drag FrequencyID in TblFrequency and drop it on FrequencyID in
TblReport. Look in the Help file for Referential Integrity and Cascade
Update and Cascade Delete to see what they are all about. (Hint: You want
Referential Integrity for all your relationships but no Cascade Delete.
Cascade Update is optional.)
Regarding autofilling, that is done by basing your form on an appropriate
query and has nothing to do with relationshipd other than relationships
determine which tables you are able to join in a query.
By The Way, what do you think of the likes of John Marshall? He has no help
to offer you but merely shows a malicious personnal attack upon me. Do you
think that is appropriate conduct for an MVP?
Steve
Raven said:
Thanks for the assistance, Steve.
The Frequency field is used to determine how often the report is run. ie,
monthly, daily, etc.
I was able to create the ids as you specified and entered them on the
respective tables. However, would I just create the link on the
relationship
tab or should I use the join or enforce referential integrity? Because,
when
I start creating the form, I would will use combo boxes to autofill or
sync
to other related fields. For instance, when the "customer" name is
entered
or selected, the "location" field is automatically filled. So, I just
want
to make sure that I am linking the tables correctly in order to make this
process work, effectively. Hope that makes sense.