Can we see the SQL being used?

I am using combo box that is writing the SQL. I have a Client Table with a Text Field named "Country". I have Country Table with a list of countries. The combo box selects a country from the Country Table and writes the Country ID to the "Country" text field in the Client Table instead of the name of the country. When I run a query of what clients are from what countries, I only see the country ID and not the name of the country. My users don't want to have to cross reference country ID's so read the query or report.

Here is the Combo Box SQl
SELECT [CountriesT].[ID], [CountriesT].[Countries] FROM CountriesT ORDER BY [Countries];

I know it is something that I am doing wrong, but I don't have these issues when I use Lookup controls instead of Combo Box. Dataverse also automatically creates relationships using Lookup fields. I don't think DV likes Combo boxes, so I may have no choice to use Lookup controls going forward.

You'd normally want to store the ID
Then use a query to grab the name

Copy that. Normally that is the solution, but I am developing, or attempting to develop a hybrid solution using Dataverse tables and local tables. Adding and Foreign Key to a DC table and relating is a challenge. Trying to figure out how that works in DV. Anyway, I think DV is presenting the problem.

So what is the bound value?
If you've got a combo with a hidden ID it's going to use that, if you don't need the ID remove it, or make it the second column and make the width 0

A combo box can store multiple columns in its row source.  The first column is always the bound column.  You can include related info in subsequent columns.  If the country name is in the 2nd column, you can retrieve it with:   MyComboBox.Column(1)

Thanks Alex and Kevin. I resolved my issue as I figured out what was happening on the Dataverse table.

What was happening?