One more file ... the form.
1) How's that again? "Alpha 4"? Don't see any field in your relationship graph or your layout with that name. What do you mean by that? Your ID's should be auto-entered ID's--Either serial numbers or Get ( UUID ). DO NOT use the person's name or a calculation including their name as the ID field linking one table to another in a relationship. Names are not unique, subject to change, and vulnerable to data entry errors--all of which causes problems for your system that can be avoided by using an ID number or Get ( UUID ) instead.
If you define your Value lists for entering an ID as a value list where the first field is the ID number and the second is a calculation field that combines names fields to produce a full name with the last name listed first, you'll get your alphabetical list of names, but the value entered when a name is chosen will be the ID in order to properly link your record.
Note, the above value list is the "beginner level" approach. It is a good starting point for setting up your database, but not the most user friendly approach once your list of names starts to increase in size past a half dozen or so names. More sophisticated, script enhanced methods may also be employed for searching by name that still enter the needed ID once that name is selected/found by the user.
OK ... I will change from the 4 digit unique alpha to a number that the user doesn't see. I will try it and see how it works. How do I do the rest after I do that. I'm a newby. Been years since I've databased and I'm used to HUGE corporations where I'm the manager and ask the techies to do this for me. I define ... they help to make it happen. I will get there. I understand data ... I just need to learn.
2) a value list is a value list. Once you have one defined and working for you in field 1, You can use it for other fields in the same layout.
3) Put Physicians and Employees in the same table. Give them the same unique ID number field. Now your value list lists both physicians and employees. Add a field to this table to distinguish Physicians from Employees. If you need other value lists to list only physicians and/or only clinical staff, you can use conditional value lists to list only personnel from a specified category.
So ... what is the more sophisticated, script enhanced method? What is it called so I can learn it and employ it? I learn VERY quickly!
There are multiple possible methods. Here are some demo files you can examine:
Simple auto-complete enabled name look up:
FileMaker 12 users: https://dl.dropbox.com/u/78737945/SimpleNameLookupDemo.fmp12
Pre FileMaker 12 Users: https://dl.dropbox.com/u/78737945/SimpleNameLookupDemo.fp7
Other "enhanced selection methods" (5 different methods demoed on one layout):
If you are using FileMaker 12. Open this last file from your File menu to get a copy converted to the .fmp12 format.
And here are my links on conditional value lists--which can be a way to list only sub sets of all the possible values in a value list:
There's a lot of overlap between the first two links so you can read one and skim the other. The demo file gives you several examples of different conditional value lists so you can examine them to see how they are set up. If you are using FileMaker 12, you can open this demo file from your File menu to get a converted copy of the demo file that you can examine in FileMaker 12.
The last link discusses how to set up a chain of conditional value lists where the value selected in each conditional value list controls the values listed in the next value list.
Forum Tutorial: Custom Value List?
Knowledgebase article: http://help.filemaker.com/app/answers/detail/a_id/5833/kw/conditional%20value%20list
Hierarchical Conditional Value lists: Conditional Value List Question
Feel free to post follow up questions here if those links aren't enough to get your value lists working correctly.
Phil ... you have helped SO much! Thank you. I will forge forward. SO appreciate your time!!
I'm not kidding you! This is SO helpful! Thank you!