Master child relationships

[muckypup]

Hi there,

I have a question regarding a standard d/loadable database called "sales contact management database". All you need to do to download it is type the name into MS Access (I'm using 2003) help. I am using it is a template to develop my own and teach myself as I go along. So if my attempt to explain the issue is a little skewiff you could always take a quick look.

There is a tab called 'CALLS' which I am particularly stumped by. Its basically a 'notes' function. The CALLS tab has two subforms 'CALL LISTING' and 'CALL DETAILS'. Both of the subforms are derived from the same table. CALL LISTING is displayed as a datasheet and lists [time], [date] and [subject] of each call as input by the user. CALL DETAILS displays as a single form and shows only [notes]. The main form is called CONTACTS.

This is the problem: As the user scrolls through each [subject] on CALL LISTING the concurrent [note] on CALL DETAILS scrolls as well. I can't work out how this is done. CALL LISTING says it is linked master child to the main form (by the field [CALLID] if I try to look at the link by clicking on [...] I get the message "PARTS OF THE LINK WITH MISSING PAIR FIELDS WILL BE IGNORED'

I can remove the master child relationship and re add it but not by using the field chooser. Try as I might I can not replicate this in my own database!!!!!!!! What is going on here? Any help gratefully received

 

[HiTechCoach]

... (by the field [CALLID] i ...

Actually it is no a field, but text box control that is what is used by the second sub form as the master linking field.

The second sub form is actually link to the the sub fom above it. There is a text box above the first sub form that has a reference to a control insise the first sub form.

This Microsoft template does not follow the naming convention they have own their own site. If they did, it would have been a lot easier to follow and figure out.

See:
Object Hungarian Notation Naming Conventions

Note: This is not a very good example for a well designed database for a contact manager.

 

[dfenton]

Note: This is not a very good example for a well designed database for a contact manager.

I have always thought that MS's sample databases and templates are really very badly engineered from the standpoint of best practices. I've never understood it, myself.

 

[muckypup]

Actually it is no a field, but text box control that is what is used by the second sub form as the master linking field.

The second sub form is actually link to the the sub fom above it. There is a text box above the first sub form that has a reference to a control insise the first sub form.

This Microsoft template does not follow the naming convention they have own their own site. If they did, it would have been a lot easier to follow and figure out.

See:
Object Hungarian Notation Naming Conventions

Note: This is not a very good example for a well designed database for a contact manager.

Thank you very much for your help. Much appreciated. Id buy you a beverage of your choice if I could but as this is the internet and we seem to be on opposite sides of the world ... I'll just ad to your reputation

Do you know of a good contact management DB template I could have a look at?