Re: ADO.net: 3 Data Set Questions (Issues)
From: Earl (brikshoe_at_newsgroups.nospam)
Date: 06/27/04
- Next message: Mr. B: "Re: ADO.net: 3 Data Set Questions (Issues)"
- Previous message: SteveC: "ADO & Tandem non-stop"
- In reply to: Mr. B: "Re: ADO.net: 3 Data Set Questions (Issues)"
- Next in thread: Mr. B: "Re: ADO.net: 3 Data Set Questions (Issues)"
- Reply: Mr. B: "Re: ADO.net: 3 Data Set Questions (Issues)"
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 26 Jun 2004 20:45:00 -0500
If you are binding to a datasource that has the blanks within, the easiest
way is to prevent the blanks from populating when you initially pull the
data. A lot of different ways of writing your query to do that, but
basically do not return the null cells. If you are using a stored procedure,
one way is to write subqueries for each field to filter out the nulls/empty
cells.
"Mr. B" <User@NoWhere.com> wrote in message
news:16vrd0ddliruqv2envnr4kmv9dqthp2pk8@4ax.com...
> With Deft Fingers, "Earl" <brikshoe@newsgroups.nospam> wrote:
>
> > IsDbNull and use a DataView for each combo
>
> Well... that solved all but Issue Two:
>
> > Issue Two:
> >
> > For the above, How can I get rid of any blank lines when I bind the
> >Datasource to a ComboBox pull down? Column 3 will have 50 lines of
blank. So if I
> >sort a ComboBox, the first 50 lines are blank! :(
>
- Next message: Mr. B: "Re: ADO.net: 3 Data Set Questions (Issues)"
- Previous message: SteveC: "ADO & Tandem non-stop"
- In reply to: Mr. B: "Re: ADO.net: 3 Data Set Questions (Issues)"
- Next in thread: Mr. B: "Re: ADO.net: 3 Data Set Questions (Issues)"
- Reply: Mr. B: "Re: ADO.net: 3 Data Set Questions (Issues)"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
|