My understanding is that the purpose of the Employee name is only to facilitate the addition process from user's perspective. Having the Employee name as a field in the training class table sounds like breaking the data normalization, as the name is obviously stored in another table, right?
That is why I can suggest you the following:
+ Use a foreign key column, so that the Employee name is directly viewable when inserting a new row. You can even create such a datasource for the Emplyoee dropdown, so that both the Employee ID and Name are visible.
+ Use a popup edit form with a template, and the Employee name will be displayed next to the selected Employee ID for informational purposes. The actual Employee name field will not be shown in the popup, but you can display it in the respective row after the Grid gets rebound after the editing is complete.
Alternatively, you can use a template for the Employee ID field, so that the name is loaded in the same cell during editing.
Finally, you can make the Employee name field editable, but use a template for it, which includes a readonly textbox, so the user will not be able to modify it manually, but you will be able to modify it programmatically.
the Telerik team
Join us on our journey to create the world's most complete HTML 5 UI Framework - download Kendo UI