You don't need a relationship to create a drop down list. I created a sample app, but if your questions / answer are long you might want to consider another method than a drop down list.
Thank you. I created a table and a layout based on that table. Each record had a header as the question and the body as the answer (some were long). I ended up making a custom help menu with a script for each question that brought up the correct record. There were 17 questions so not too many.
Still, for the future, I am looking for a way to put a drop down list of faqs on each visible layout on the database. I am wondering if I have to make a table occurance and form a relationship for each table occurance that the layouts are based on? If so, I am not sure how to relate them. Tables include CLIENTS, JOBS, INVOICES, TASKS, PROPOSALS, ADMIN. Those are also the names of the layouts.
A relationship is not required for a drop down list.
You can create a relationship to show the answer after the question is selected. Create a relationship between the dropdown field and the question field.
I updated the sample file. Maybe this will work better for you.
In the sample I made the dropdown field a global field which could be used on any layout.
You can change this from a global field then you would have to have a dropdown field in each table, then related that field to the question field.
Depends on your needs.
I will try this out as soon as I get off work.