Can't read your screen shot, you might try cropping your jpeg to just the dimensions of the window, then click Edit post in your message above and re-uploading the screen shot. Even when I click on it to get a larger view I just can't quite read it.
There are two 'tricks' to getting the name to display when you select a valuel from a two column value list.
Method 1: use a pop up menu and specify that the first column be hidden in the value list setup.
Method 2: add the field from the related table that stores the name to your layout. You can can even use behavior settings to deny access to the field and place it on top of the drop down list formatted ID number field so that ID field is hidden from view. When the user clicks on the visible field, the hidden dropdown pops to the front and deploys the list of values. When you exit the value list, it drops back behind the "name" field--which displays the selected name--hiding the ID number.
One thing you can do is put the "related" Description/name field on the layout next to field with the id and shrink the Idfield down to just the Dropdown arrow.
In your valuelist setup you can select 2 fields and the display only values from second field.
What will result is the related name will be displayed in the layout but the id will be stored in your table.
If you need more detail let me know.
Ninja'd by Phil yet again :)
I have tried to use photobucket because I could not seem to get the image right for viewing. Please let me know if you still cannot view this.
Don't see any obvious issues with your relationships.
Outstanding. I tried the suggestion by Aammondd regarding putting the field from the other table and shrinking the Id field and that works perfect, this will be quick fix just to be sure everything is running well and then I will go back and fancy it up using Phil's suggestion. Thank you. My next question is for the join tables do I have to use a portal in order to have them be able to enter data into the joins and is there a way to automatically have it import the ID number from the main table into the join table instead of having to input this information twice. (am I clear on my question) it is hard to ask questions when you arent very good at the system you are asking about. Please let me know if you dont understand and I can try to explain it with an example in my db.
Thanks again, you guys are great!!!
If you enable "Allow creation of records via this relationship" for Device_Container in the Device to Device_Container relationshiop, You can put a portal to Device_Container on your Device layout. Then, add a drop down list or pop-up menu for selecting the Container ID inside this portal. With this set up, when you select a container in the bottom blank row of the portal, FileMaker automatically creates a new record in Device_Container and enters the value of DeviceID from the current record into Device_Container::DeviceID_fk for you to link it to the current device record. Your selection of a container ID then completes the link to a container record.
You don't have to use a portal like this, but its a very convenient way to set things up any time you need to see/work with multiple related records such as you have here.
Here's many to many demo file you may want to look at for how this can be set up:
Also, to help make the transition from Access to FileMaker, any place you might use a sub form or sub report in Access is where you would most likely use a portal in FileMaker--they are very similar.
Phil, I am using your suggestions and am looking at your file for help. I was trying to figure out how you hide the ID in your contracts pop up to where it is just showing the Contract and not the ID.I am using drop downs since my lists will be long. Should I try the same thing as suggested before where I just make the dropdown arrow smaller and then pull the file from the other table of the information I want listed, will this work in a portal the same way as it does on the main layout? I didnt see any settings for hiding in the behaviors part of filemaker and I am sure it is something simple.
In Manage value lists, there's an option named: "show only values from second field". With that enabled, the value list only displays the 2nd "name" field in the value list. If you use this value list with the pop up menu format, the pop up menu also displays only the wnd field value even though the first field value is stored in the field. If you choose to use a drop down list format, you'll see the first field value (the ID number) in the field once you exit the field. This is were it is sometimes useful to use a drop down list with but put the related table's "name" field on top of the drop down list like I described earlier.
When you're ready for a look at more ideas, let me know. I have a demo file where a combination of scripts and layout tricks make it possible to have an auto-complete enabled drop down list of names that selects and enters the correct ID number--while managing the occurrence of any duplicate names in graceful fashion.
I would love to see your solution that is more graceful. Sorry to ask, may be a silly question and something really easy but I am still not seeing in the behavior selection how to lock the field from being able to enter information. I have hidden my ID field to where just the dropdown is showing and have put a new field (edit box) for the actual name of the component. I dont want the person entering the information to be able to change the title ( I dont have the allow add or delete selected in my database manager but I dont think that will save them from changing anything that is already entered. any suggetions on this?
Enter layout mode. Select your field on the layout. In the inspector, select the data tab. About halfway down is a section titled "behavior". In "field entry" clear the browse check box and no user will be able to edit the selected field(s) on that layout.
I'm going to post the link to the demo file here. It demos several different ways to "name search" out data on an imaginary invoice form--which just so happens to populate data in a portal much like you are needing to do here. I wouldn't spend much time on it until you get the basic value lists working for you as the tricks in this demo file rely on the same techniques, but then enhance the user input with scripts to make working with lengthy value lists much easier.