yes, it will be hard for us to check one by one on the numbers...
because the combo box seems to work just the output on the database is kinda wrong...
The combo box setup is actually correct. It is intended to store a foreign key id or primary key id in a table.
From that table you create a query to pull the data (including text) that you wish to see. To do this you just include two tables in the query, the main one with main data, and the secondary one with static data.
I'll give you an example from one of my databases of how this works:
I have a Recipe table with this structure:
Name: tblRecipe
RecipeID AutoNumber Primary Key (PK)
RecipeDesc Text
RecipeName Text
RecipeTypeID Number Foreign Key (FK)
Second table: Name tblRecipeType
RecipeTypeID AutoNumber PK
RecipeType Text
You will notice that in my main table I'm storing a Number that links to my second table's primary key. This is called a foreign key.
In the table tblRecipeType I have this data: Dessert, Main, Breakfast, etc...
Now I create a new recipe, and through a combo box choose Dessert for the recipe type. This stores the number value 2 in my tblRecipe. How do I know what a 2 means?
In a query I do this:
- SELECT tblRecipe.RecipeID, tblRecipe.RecipeName, tblRecipe.RecipeTypeID, tblRecipeType.RecipeType FROM tblRecipe Inner Join tblRecipe ON tblRecipe.RecipeTypeID = tblRecipeType.RecipeTypeID WHERE tblRecipe.RecipeID = Forms!frmRecipeDetail!cboRecipe
When I run this query I get the RecipeID, Recipe Name, Recipe Type ID and Recipe Type (text name) from the chosen Recipe on my form frmRecipeDetail with a combo box called cboRecipe.
Now... Take a good look at your database, and see how the structure is either the same as what I'm referring to, or different than. Then read this tutorial carefully:
Database Normalisation and Table Structures
I suspect what is really happening is that you are trying to apply a properly designed combo box setup to an improperly designed database, or are just not understanding how to use the design to display what you want to see.
Regards,
Scott