Susan Harkins
ssharkins at bellsouth.net
Thu Jul 8 09:15:46 CDT 2004
The bound column is the first column -- CustomerID, which of course, screws things up. However, I set those properties manually when I created the list box. I guess I could force th issue by setting them programmatically when I load the form and populate the control -- but still doesn't explain why it happens. :( Susan H. Is it related to which column of the listbox you bind? /gustav > Ordinary SELECT Gustav -- > "SELECT CustomerID, CompanyName, Phone, Fax FROM Customers" > Simple as pie. > But remember, I'm populating the list box via the Recordset property - > - and that's what seems to mess it up -- so whether it's some peculiar > behavior of the Recordset object, the property, or the list box I can't tell. > Susan H. > Hi Susan > Oh, sorry, missed that point. > I have no idea - never observed that. > What does your Select statement look like? "Select * .." or "Select > Company, Customary .." > /gustav >> Column Heads should simply display the column names in the first row >> -- not rearrange the columns. The SELECT statement retrieves >> Customary and Company Name -- in that order, but the list box >> displays Company Name first. That's what I meant by "transposed." >> Susan H. >> Hi Susan >> Ehh ... That's by design ... >> What else would you suggest a property of this name should address? >> /gustav -- _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com