> It depends how the data is connected.
>
[quoted text clipped - 42 lines]
> >
> > Thanks
Answers embedded in-line.

Signature
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.
> Hi Allen
>
[quoted text clipped - 11 lines]
> Question 1
> Can I place the other 3 tables on the form as subforms to enter the data?
How do these 4 tables relate to each other?
a) One table has 3 related tables, e.g.:
Customer => Order
Customer => Payment
Customer => Address
In this case, you could bind the main form to the Customer table, and use 3
subforms for the 3 related tables.
b) Each table has a related table of its own, e.g.:
Customer => Order
Order => OrderDetail
OrderDetail => ItemsSent
In this case it is probably best not to try to use one form to handle it
all. You might get away iwth Orders as the main form, with 2 subforms - one
for the OrderDetails and the other for the ItemsSent. There's an example of
how to do that in Northwind - the Customer Orders form from memory.
It would possible to place that whole thing on the Customers form, but I
think that's getting messy.
> Question 2
> What property would I set to make the subform frames merge with the main
> form to give the appearance that all controls belong to the main form (ie
> hide the subform frame).
Assuming structure (b) above, see the Northwind form for how to set the
LinkMasterFields. There are actually 2 ways to do this. The other way is a
hidden text box on the main form with properties:
Control Source =[OrderDetailSubform].[Form].[OrderDetailID]
Name txtOrderDetailID
so you can use txtOrderDetailID in LinkMasterFields for the ItemsSent
subform.
> Question 3
> I would like on this occasion to use the above method but.......
> What would be considered the "best practice" method of entering the data
> into the 4 table in this hypothetical example.
Best practice is subjective. You have several goals. After reliability (it
works without fail), simplicitiy and comprehendability for the end user are
high priorities. That means keeping the interface as uncluttered as
possible, and I suspect trying to handle all 4 levels in a single form will
be too much.
If you really need to handle them all in one form, a tab control might save
your bacon. The first tab could handle all the customer details, and the 2nd
tab could be filled with the form constructed above (as a subform.) Can't
say I really recommend that, but I can't see your data.
> Thanks
> Dermot
[quoted text clipped - 50 lines]
>> > Can anyone explain to me what I have overlooked and let me know what I
>> > should expect here?
Dermot - 11 Mar 2007 21:54 GMT
Hi Allen
Thanks for the reply and explanation of the different possibilities to
consider with respect to the related table posibilities.
On this occasion I was referring to you explanation a) below.. and all one
to many.
How do these 4 tables relate to each other?
a) One table has 3 related tables, e.g.:
Customer => Order
Customer => Payment
Customer => Address
In this case, you could bind the main form to the Customer table, and use 3
subforms for the 3 related tables.
I do take you suggestion wrt everything looking to cluttered.....and keeping
it simple....Using your example above.....creating the main form bound to the
customers table.....I then placed 3 subforms in the other 3 quarters of the
form and created 3 comand buttons with code on click event to change the
visible property of each form so at any one time only the main form controls
and the controls on each subform would show on click event of the appropiate
command button.....I am not sure I like this.....a bit odd!!!
The other option I considered was to create a Main form with the most used
info subform in it and create two separate data entry forms for the other two
tables acessing all from a switchboard form.....and drop the additional
subforms.
I think from all this ......I have learned that subfroms are not the best
choice for overall data entry...they are more useful for viewing / editing
further details relevant to a main form.
I will take your advise and have a look at Northwind....if you have any
further comments you would care to part with before I move on from this
posting it would be very much appreciated.
Thanks
Dermot
> Answers embedded in-line.
>
[quoted text clipped - 117 lines]
> >> > Can anyone explain to me what I have overlooked and let me know what I
> >> > should expect here?
Allen Browne - 12 Mar 2007 01:58 GMT
You might like to try the tab control, with 4 tabs:
- The first tab page contains the main table's fields;
- Tab pages 2 - 4 contains a subform for a related table.
I use that all the time. The only issue is that the user can't see which
customer this is when they are on a secondary tab page. To solve that, add
some code to the Current event of the form, to place that info in the form's
caption. Something like this:
Private Sub Form_Current()
If Me.NewRecord Then
Me.Caption = "Customer: New Record"
Else
Me.Caption = "Customer: " & Me.[FirstName] & " " & Me.[Surname]
End If
End Sub

Signature
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.
> Hi Allen
> Thanks for the reply and explanation of the different possibilities to
[quoted text clipped - 188 lines]
>> >> > I
>> >> > should expect here?
Dermot - 12 Mar 2007 03:01 GMT
Hi Allen
Many thanks for the suggestions. I will try this out.
Kind regards
Dermot
> You might like to try the tab control, with 4 tabs:
> - The first tab page contains the main table's fields;
[quoted text clipped - 205 lines]
> >> >> > I
> >> >> > should expect here?