problems connecting fields

[accrep18]

I'm tying to make a relationship between Photo (an attachment field in Table 2) with the same in Table 3.
I created each Photo field separately in each Table.

I get an error - see attached.

I'm missing something simple... I want to just upload a photo attachment in Table 2 and have it auto-populate in Table 3.


How to do this correctly ?

Thanks !

[ranman256]

you dont relate photos, you relate the Key IDs
ID --> ID

And the ID must be keyed 1 master to N child.

[accrep18]

I have a Key ID that relates all 3 tables (see screenshot).
So does that mean that if I enter a already-existing field from Table 2 into Table 3, that it would auto-populate ?

Can I make Photo a Key ID for Table 2, and then relate it to Photo in Table 3 ?

[orange]

Here's a link on database planning and design with a number of articles, tutorials and videos that should help with concepts.

It is helpful to you and readers if you describe what you are trying to do in plain English. Add graphics or tech/database jargon if needed.

[accrep18]

Thanks for the links - I understand better.

I guess the question I have is :

-are there situations where you want to have the same (non-key) field in two different tables ? (Photo, in my case)
-if so, how do you ensure that those fields track/update when a change is made in one table vs another ?

Here's a link on database planning and design with a number of articles, tutorials and videos that should help with concepts.

It is helpful to you and readers if you describe what you are trying to do in plain English. Add graphics or tech/database jargon if needed.

[orange]

are there situations where you want to have the same (non-key) field in two different tables ?

Possibly, but that's sort of hypothetical.
The concern here is what exactly are you trying to do in simple, plain English? No database, no jargon.
Once we know what and understand, readers may offer advice/suggestions as to how it might be done with Access.

[accrep18]

What I'm trying to do is have a photo (image) available for the user whenever they are in Table 2 or Table 3.
Actually Table 3 will be tied to a Form, where the image would be shown.
One image per record.

[orange]

??? You can do better than that for a description of what you're trying to do in plain, simple English.
Consider, you are in a line at McDonalds, then person behind you --who does not know you, does not know database --asks you what your project is about? Instead of telling him or her to get lost, you simply tell them in plain, simple English.....

Here's an example from a tutorial from the link I gave you earlier

Problem Narrative:
Class Information Database


Roger Carlson's CIS 253 class wants to create a database to store information about the students in the class. Information will include student demographic information, contact information and course information and history.

Information about the students will include name, address, city, state, zip, phone, email, fax, college major, Social Security Number, and gender. Each student can have more than one phone number, email address or fax number.

Course Information includes course name, course number, number of credits, and grade received. Each student will take many courses in their college career. And naturally, each course will have many students enrolled.

[ssanfu]

Storing pictures/photos in tables is the WRONG approach!

Here is an explanation why (and a tutorial): Storing Pictures In An Access Database

[orange]

Nice link Steve.