DropDown's DataSource/DataMember

[John Spiegel]

Hi all,

I think I've stared at it until it's made me stupid(er?). What am I missing
about setting the list of the dropdown to display data pulled from a table?

//...
daPrepaid.Fill( dsPrepaid, "Seller");
cboSeller.DataS ource = dsPrepaid.Table s["Seller"];
cboSeller.Displ ayMember = "Name";
//...

When I assign the datasource, the dropdown's Text property changes to
"System.Data.Da taRowView", which is then the only item in the list as well.
What's the stupid thing I'm not seeing?

TIA,

John

[Greg Burns]

Aren't you missing the cboSeller.Value Member="Name"; <-- or whatever field ?

Greg

"John Spiegel" <js******@YETAN OTHERSPAMHATERc-comld.com> wrote in message
news:eL******** ******@TK2MSFTN GP10.phx.gbl...

Hi all,

I think I've stared at it until it's made me stupid(er?). What am I
missing
about setting the list of the dropdown to display data pulled from a
table?

//...
daPrepaid.Fill( dsPrepaid, "Seller");
cboSeller.DataS ource = dsPrepaid.Table s["Seller"];
cboSeller.Displ ayMember = "Name";
//...

When I assign the datasource, the dropdown's Text property changes to
"System.Data.Da taRowView", which is then the only item in the list as
well.
What's the stupid thing I'm not seeing?

TIA,

John

[Cor Ligthert]

John,

A change is in my opinion that "Name" is in the wrong case or even not in
your select..

That because you use three words cbo (combobox) and DropDown.

When cbo is a webpage dropdownlist than it is easy.
You miss
cboSeller.DataB ind();

I hope this helps?

Cor

[John Spiegel]

Hey Greg,

I had it in, but was getting an error. The strange thing is when I do
include ValueMember, the error message indicates a problem with binding to
DisplayMember, more specifically:

Could not bind to the new disply member.
Parameter name: newDisplayMembe r

A less abbreviated snippet...

OleDbCommand cmdPrepaid = conPrepaid.Crea teCommand();
cmdPrepaid.Comm andType = CommandType.Tex t;
cmdPrepaid.Comm andText = "SELECT * FROM PrepaidSeller";
daPrepaid = new OleDbDataAdapte r();
daPrepaid.Selec tCommand = cmdPrepaid;
dsPrepaid = new DataSet();
conPrepaid.Open ();
try
{
daPrepaid.Fill( dsPrepaid, "Seller");

cboSeller.DataS ource = dsPrepaid.Table s["Seller"];
cboSeller.Displ ayMember = "EntityName ";
cboSeller.Value Member = "CustKey";
//...
}

Thanks,

John

"Greg Burns" <greg_burns@DON T_SPAM_ME_hotma il.com> wrote in message
news:%2******** ********@TK2MSF TNGP15.phx.gbl. ..

Aren't you missing the cboSeller.Value Member="Name"; <-- or whatever field ?
Greg

"John Spiegel" <js******@YETAN OTHERSPAMHATERc-comld.com> wrote in message
news:eL******** ******@TK2MSFTN GP10.phx.gbl...

Hi all,

I think I've stared at it until it's made me stupid(er?). What am I
missing
about setting the list of the dropdown to display data pulled from a
table?

//...
daPrepaid.Fill( dsPrepaid, "Seller");
cboSeller.DataS ource = dsPrepaid.Table s["Seller"];
cboSeller.Displ ayMember = "Name";
//...

When I assign the datasource, the dropdown's Text property changes to
"System.Data.Da taRowView", which is then the only item in the list as
well.
What's the stupid thing I'm not seeing?

TIA,

John

[John Spiegel]

Hey Cor,

That's interesting. It was the case! I had used mixed case naming in
another piece a few days ago--but that was in a typed data set.

Thanks!

John

"Cor Ligthert" <no************ @planet.nl> wrote in message
news:%2******** ********@TK2MSF TNGP11.phx.gbl. ..

John,

A change is in my opinion that "Name" is in the wrong case or even not in
your select..

That because you use three words cbo (combobox) and DropDown.

When cbo is a webpage dropdownlist than it is easy.
You miss
cboSeller.DataB ind();

I hope this helps?

Cor

[Cor Ligthert]

John,

Always the same problem and than I forgot it. You cannot use reserved SQL
words as items and AFAIK is "Name" one of them.

Cor

[Greg Burns]

> A change is in my opinion that "Name" is in the wrong case or even not in

your select..
Cor, I don't believe case-sensitivity matters. No?

If this were a web page, the dropdownlist binding would look something like
this:

ddlSeller.DataS ource = dsPrepaid.Table s["Seller"];
ddlSeller.DataT extField = "Name";
ddlSeller.DataV alueField = "NameID"; <-- change appropriately
ddlSeller.DataB ind()

' optional...
ddlSeller.Items .Insert(0, New ListItem("-select a Name-", ""))
If it is a combobox on winform, then:
cboSeller.DataS ource = dsPrepaid.Table s["Seller"];
cboSeller.Displ ayMember = "Name"
cboSeller.Value Member = "NameID"; <-- change appropriately

Personally, considering all the troubles I've had databinding with winforms
(selectedindex=-1 issues, bound controls on tabcontrols, etc.) I prefer to
just iterate the datatable and manually add the items. But that's just me.

my .02
Greg

Greg
"Cor Ligthert" <no************ @planet.nl> wrote in message
news:%2******** ********@TK2MSF TNGP11.phx.gbl. .. John,

A change is in my opinion that "Name" is in the wrong case or even not in
your select..

That because you use three words cbo (combobox) and DropDown.

When cbo is a webpage dropdownlist than it is easy.
You miss
cboSeller.DataB ind();

I hope this helps?

Cor

[Cor Ligthert]

Greg,

I saw that afterwards the same as you, that it could not be a webform
because that the dropdownlist has not a displaymember.

However than had John already sent a message replying you, I replied that
and after that he came with the answer that is was a case situation.

However I am still not sure if it was the case situation here or the wrong
itemname.

However the "case" is important in this situation (I have seen this to often
in this newsgroup while it is as well my own expirience). And the strange is
with that that SQL is case insensitive.

However just as far as I know.

Cor

[Greg Burns]

Hmm.

I too was confused about winform and webform. :)

I thought you were onto something with the reserved word thing.

And the strange is with that that SQL is case insensitive.
"In SQL Server, object names can be case-sensitive, depending on the
character sort order that is installed. The sort order is chosen in SQL
Server Setup during installation. The default sort order in SQL Server
is dictionary order, case-insensitive.

If you need to change sort orders after installation, you must rebuild
your databases and reload your data."

John, try typing "execute sp_helpsort "in Query Analyzer to see what the
sort order and case-sensitivity is of your server. I know I am curious. :)

Greg

"Cor Ligthert" <no************ @planet.nl> wrote in message
news:uD******** ******@TK2MSFTN GP12.phx.gbl... Greg,

I saw that afterwards the same as you, that it could not be a webform
because that the dropdownlist has not a displaymember.

However than had John already sent a message replying you, I replied that
and after that he came with the answer that is was a case situation.

However I am still not sure if it was the case situation here or the wrong
itemname.

However the "case" is important in this situation (I have seen this to
often in this newsgroup while it is as well my own expirience). And the
strange is with that that SQL is case insensitive.

However just as far as I know.

Cor

[John Spiegel]

Sorry, I had been silly in my editing. The actual field name was
"EntityName "--which is what I was using on the .NET side as well...

"Cor Ligthert" <no************ @planet.nl> wrote in message
news:uI******** ******@TK2MSFTN GP12.phx.gbl...

John,

Always the same problem and than I forgot it. You cannot use reserved SQL
words as items and AFAIK is "Name" one of them.

Cor