Container Relationship

[redballoon]

Hi,

I have a database I am trying to create using a load of images. Firstly I imported the image as a refrence to the file it's self. I would like another databse to have a relastionship with the image database and allow the user to choose an image to import however I cannot get past the relationship stage as it seems you cannot define a relationship to a container field. Is there any way around this ?

[Søren Dyhr]

To use another fields value or contents must an indexable key field exist to reference or distinguish from the rest.

There isn't much point in looking up or importing since a referenced value usually is all it takes to make it visible, otherwise will the redundant storage of several occurrences make the file-size grow exponentially by the use of it.

Why would you like to make the container field it it self a relational key, a key value should be indexable ... how practical would that be if you have a 1000 images of a soccer-match, the greenish pixels would be pretty dominant, how would you sort on it? Is it if a bunch of players in white jerseys occurs in upper left corner or??

I would save the machinery the bother and name each image with something short and concise in an extra field, which isn't what I would see as a work around. Pattern recognition would require a native algorithmic approach that would pull a database out of it's realm if we look strictly at it, wouldn't it?

--sd