I've been doing so much reading over the last week on value lists and relationships.

I've tried so many variations that I thought should work, that I went back to a brand new database to check my sanity.

My structure is three tables: Arrangements - Organisations - Contacts

'

For clarity I don't have Contact Names or Organisations Names.

I've got two Value Lists:

Organisations  (which is just an unfiltered list using Organisations::OrgID

Contacts (which is from Contacts::ContactID.  Including only relevant values starting from: Organisations)

 

This works perfectly - I create a new record in Arrangement, choose from the OrgID Popup Menu (Organisations Value List)

Then the ContactID Popup Menu only shows me the list of ContactIDs that have that OrgID in their records.

 

My problem - same structure in my main database.  I know I had it working at one stage, but got sidetracked for a few days trying to solve some other part of the database.

When I came back to this - it didn't work.  I have quadruple-checked (and more), that I don't have any scripts, calculations or anything connected to any of those fields or layouts.

I've created new layouts, new fields, new value lists with every possible permutation.   But as soon as I try to filter that Contacts Value List - I just get <no values defined>

I've got to be missing a tiny setting somewhere, but my searches aren't helping. I really don't want to have to start my db from scratch!

 

8 hours ago, Bullion said:

My problem - same structure in my main database.

If it doesn't behave the same way, then obviously something is different. But we have no way of telling what that something is.

Why don't you make a copy of your file and start removing everything until you reach the "skeleton state" described in your question. If you do not discover the problem in the process, then post the resulting file.

 

In my experience these thing usually fail when one of the fields is not indexed/indexable, and therefore the value list just quietly fails.

Have you deliberately turned off indexing for the one the fields involved in the relationships?

Was hoping that there would be something basic that I had missed before I try stripping it back or rebuilding it! But if I have to do that, then…sigh…that’s what I’ll do!

rwoods: thanks, I’ll check that out when I get to my computer!  Here’s hoping I’ve accidentally done that. Certainly didn’t do it on purpose!

Coming back to report that, unfortunately - all of the ID fields are indexed. So it's not that.

Next step is to strip it back to bare bones...

 

EDIT:

Second report for anyone who might be searching for the same issue.

I can't believe how stupid this is... I had somehow turned on "auto-enter a value" for the OrgID foreign field in the Arrangements table.

So instead of that field being related to the OrgID I had chosen in the Arrangements layout, it was being automatically filled with an unrelated serial number. So simple.

Edited May 3, 20223 yr by Bullion