I don't know what's wrong. Maybe it's better that you build a compilable project using SQLite that reproduces the problem so I can compile, run and debug it. When it gets to this point it's not very productive to start doing too many guesses.
Ok, thank you in guessing so far, but it means that I DO NEED to have the COLUMN property tag for UNIDADE: TEntityUnidade. I was not sure that was needed or not.
So i will see what is wrong around this.
From what I understand from all this discussion:
your combo must have a list of existing TUnidade objects. You made it.
Your TItemProduto must have a property named Unidade: TUnidade; You should then bind Combo.SelectedValue to ItemProduto.Unidade so when user chooses one TUnidade object from the combo, the TItemProduto.Unidade is set with a reference to that object.
That's how it should work from my understanding of your setup.
Wagner,
Problem SOLVED !!!!
Let me explain where was the problem.
There is no need to have the UNIDADE and FORNECEDOR declared as COLUMN tag on the entity.
The problem was that at very begining I have entered MANUALLY the fields, when I double clicked the TAureliusDataset.
After some time I have decided to go the package way to load the field and did not pay attention to the fact that the fields displayed on the TBindSourceDB came from the MANUALLY ENTERED FIELDS and not from the loaded ones.
So, I deleted all the fields entered and then loaded the entity TEntityItemProduto (the one on the top) again and reseted the connection with the TBindSourceDB.
The result was that TBindSouceDB now show all the fields INCLUSING the ASSOCIATIONS (as variants like you say on the help file)
Then I have made the bind as follow: http://snag.gy/vO2EK.jpg
And WORKED VERY WELL!!!
I am so happy that worked, that my structure is now correct.
Thank you for you great support and for this wonderful framework that TMS created. I will be sharing my experience with other developers about this!