Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

DBLookupComboBox Problem

Status
Not open for further replies.

Oppenhiemer

Programmer
Jun 28, 2001
315
GB
Hi -
When I place a DBLookUpComboBox on to a form and fill in all the necessary details, the component seems to work fine - expect that it
does not show the value of the field selected (its just blank.)

I know the value is actually being stored, as if I place a regular field component and set it to the field in question - I can see the
value (and see it changing when a new value is selected.)

As far as Im aware, I have set all the properties correctly and have tested it with a table-vesion of the same app; and this seems to work.

I only seem to have this problem when using ClientDataset components to feed the control. I was wondering if it was perhaps an issue with the transaction components ? Even though all other controls seem to be working as expected and showing the data.

So in summary, the "DateField" value is not being displayed properly - even though it is being stored.

Any help would be much appreciated..

Thanks..

Opp.
 
Check out
How to use Look Up fields with Tables /Queries

faq102-1212

Maybe there is a broken link between the main table and the look-up table.

If you are working with datefields be aware that they are stored like real numbers, especially when you have a time stamp.

A date can be stored like 11345.2 or 11345.6.
It is the same date, but on different hours. The link will not be made unless you compare the integer portion of the fields. Integer numbers would be the best way to base the lookup proces upon.

Regards

Steven van Els
SAvanEls@cq-link.sr
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top