In regards to it not working - have you opened up the form and actually selected a jurisdiction? If you've set up the relationship and the lookup fields, then when you select a Jurisdiction on the form - assuming the fields you're using have data in your parent jurisdiction, they should populate.
As for your second question - technically that is one way to do it. You could set up 9 relationships - each with their own set of lookup fields. An alternative would be to set up a join table, basically another table that is the textbook method of handling many to many relationships as you've described. Basically what it sounds like you actually have is:
Jurisdictions have many certs
Certs have many jurisdictions
With many-to-many relationships like that - the proper way is to create a join table 'Cert-Jurisdictions' - where your relationships are:
Jurisdictions have many Cert-Jurisdictions
Certs have many Cert-Jurisdictions
This join table breaks up the many-to-many problem
In this case - your Cert-Jurisdictions table is a child to both, and you can have as few or as many Jurisdictions related to your cert as you might need. This can be tricky from a reporting standpoint sometimes. That said - you could get away with doing it with 9 relationships - its just a little harder to set up and manage.
Chayce Duncan | Technical Lead
(720) 739-1406 |
chayceduncan@quandarycg.com Quandary Knowledge Base