Depending on the solution you have maybe you can try with a global field.
And use a relation between the global field in the studen db and the lastname field on the faculty db and in the layout use student::global, and faculty::ID#.This will cause the ID to popup as soon as you type in the lastname in the globalfield and exit the field.
NOTE this solution depends on what you want to do with the database :smileyhappy:
Yaaa! Thank you Diquito. I will give it a go.
Thanks for the post.
What you describe is very much possible. It's not particularly safe though...not at all.
I make the following assumptions:
1. When you say two Dbases, you mean two Dbases. If they are two tables, ignore my reference to File References
2. Your Faculty Dbase has a field "LastName" and another field "FacultyID"
Your student Dbase field "Advisor Last Name" should be linked to Faculty Dbase field "Last Name".
Also, on your Student layout, the Advisor ID field should actually be Faculty::FacultyID (a field from the other Dbase).
If this is already the case, check that your File references are in order...that the Student Dbase correctly sees the Faculty Dbase.
That done, consider NOT using a name to trigger this relationship. Mr Jones the math teacher will get confused when all of his students show up to Mrs Jones the art teacher for advice. Jones = Jones...who's the advisor? Consider instead having a uniqueID field per faculty member (and the same for the students for that matter) and choosing your Faculty Advisor from a drop down value list based on Faculty Name (with autocomplete of value). It will get you close to where you describe as your target, but will keep record identifiability safe.
Does that make sense?
Hope this helps...
This does work really well! Thank you!! Amy :smileyhappy: