Creating Input Forms

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

In the following example I realise I could have one table "Contact Details"
but if anyone can advise on my question, it woud be much appreciated.
If I have 4 tables:-
Client Name: ID, FirstName, LastName (Text)
Phone Numbers: ID, Number(Text)
Mobile Numbers: ID, Number(Text)
Email Address: ID, Address (Text)

If I have setup relationships to reflect any one client has many Phone
Numbers, many Mobile Numbers and many Email Addreses......

My Question
Can I create one "Data Entry Form" to enter data into the tables or do I
need to create a separate Data Entry Form for each table. Using the Form
Wizard or doing it manually appears to only allow me to select one table
source at a time (I thought I would be able to incorporate the fields from
all table on the one form.

I know this may not be a great example to use but I am trying to understand
the methods available to enter data into serveral "Related Tables" as
compared with a "Flat Table"

Thanks in advance for any advice.
 
Dermot,

I suggest either two or three tables:
Client
ContactData: ContactID, ClientID, ContactType (phone num, mobile num, email,
etc), Text

If you prefer to keep Email addresses in a separate table, then three tables.

Your data entry form would have Client info on the main form and the contact
data in a subform linked on the ClientID. You can then enter an unlimited
number of phone or email addresses.

HTH
 
Thanks for the reply Sam
I understand what you are saying about the subform, I will experiment with
this.
Please advise further.......I am just trying to workout what is possible and
what is not possible....
Can I create one single "Data Entry Form" without a subform .....a quick
data entry form.......to enter data into all the separate related
tables.......without having to switch between several Entry Forms for each
table?
Thanks
Dermot
 
If your phone numbers are in different tables, you would either need a union
query or change the record source programmatically to use the same form with
the different tables. Both of these are much more complicated than using
subforms. You can make it not obvious to the user that there is a subform by
setting subform properties such as border and scroll bar characteristics. So
the form can still look quite simple.
 
Back
Top