Everything looks fine -- but when I Find I get Invalid Relationship?

[rlinsurf]

Here's a screenshot of my relationships. All the ID and IDShort numbers are long unique numbers. ID is 48 numbers IIRC, and IDShort is at least 22.

When I do a Find, say in a jotts layout, using the jottText relationship, Text field, I get a dialog saying one or more of the relationships are invalid.

What am I doing wrong?

[bcooney]

Your relationship diagram raises lots of red flags for me.

What are all the linksParse# fields?

You haven't named your fields in such a way that would allow me to determine what is a primary key and what is the foreign key. For example, you relate jotts::ID to jottText::ID. That is odd, if jottText::ID represents the primary key of another table, jottText. You should be relating primary key to foreign key.

How are your IDs set? Are they auto-enter serial numbers? Hopefully, there are, and not calc fields.

[IdealData]

Noticably the "jotts" relationship has a "blocked" line on both ID and IDShort. This means that the target fields ID and IDShort are not indexed.

If they are calculations must NOT be unstored, or the result of a related field.

Check the storage options in the field definitions and turn on indexing.

[rlinsurf]

Hi--

Absolutely perfect. I checked, and indeed they were set to unstored. When I set them to index, all is now well.

Thanks very much :

[rlinsurf]

Hi--

Heh. All those are my parsing of my downloaded webpages. Each page contains 20 links to jott's, with the text, and the url for the .mp3 audio file. First I separate each

out where the links are, then CF the links themselves, then perform the downloads.

It actually works pretty well.