[AccessD] combo box Limit to List question

I've lost track of the question by now, Susan.  In a one-column list,
the only column happens to be the bound column because there's no other
choice.  If the hidden column in a multicolumn combobox is the bound
column (it doesn't have to be) then you need to populate that in order
to create a new record.  Access doesn't care which column you bind to,
but it only knows automatically how to handle a bound first column when
values are entered into it, just as it can handle the single column
list.  Otherwise, it requires the NotInList event to do the handling.
What's unreasonable about that? Remember that the combo box can only
save *one* value, which means all the other columns are for matching or
displaying information.  If you don't populate the bound column either
by typing in a value or by using the NotInList event, Access doesn't
know what you want to enter/save.

Charlotte Foust

-----Original Message-----
From: Susan Harkins [mailto:ssharkins at bellsouth.net] 
Sent: Monday, June 07, 2004 10:32 AM
To: 'Access Developers discussion and problem solving'
Subject: RE: [AccessD] combo box Limit to List question


A one-column list can be populated with anything -- so why should Access
care which column you're restricting, as long as it knows? A new
property -- which column is restricted. If the entry violates other
table properties, that's another story -- you have that possibility with
a one-column list. 

Susan H. 

How else would you populate the bound column, Susan?  It doesn't seem
nasty to me, but perfectly reasonable.


-- 
_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com