name that tune

[=?Utf-8?B?cm9kY2hhcg==?=]

hey all,

i have a formview that contains a dropdownlist. it's datasource is coming
from a table. the selectedValue can be blank. Would it better to add a blank
in the database table or dynamically in the code-behind. And how many
routines would i need in either case? (I'm looking for the most efficient
way, am I incorrect to do so?)

Thanks,
rodchar

[Daniel]

What would a blank entry indicate?

I have never seen a need for a blank entry in a database. Not a good idea.
(unless by blank you mean a null value?)
"rodchar" <ro*****@discussions.microsoft.comwrote in message
news:69**********************************@microsof t.com...

hey all,

i have a formview that contains a dropdownlist. it's datasource is coming
from a table. the selectedValue can be blank. Would it better to add a
blank
in the database table or dynamically in the code-behind. And how many
routines would i need in either case? (I'm looking for the most efficient
way, am I incorrect to do so?)

Thanks,
rodchar

[=?Utf-8?B?cm9kY2hhcg==?=]

i think that answers my question. The blank is for the dropdownlist so that
if the selection is blank it will store a null in the database. thanks, rod.

"Daniel" wrote:

What would a blank entry indicate?

I have never seen a need for a blank entry in a database. Not a good idea.
(unless by blank you mean a null value?)
"rodchar" <ro*****@discussions.microsoft.comwrote in message
news:69**********************************@microsof t.com...

hey all,

i have a formview that contains a dropdownlist. it's datasource is coming
from a table. the selectedValue can be blank. Would it better to add a
blank
in the database table or dynamically in the code-behind. And how many
routines would i need in either case? (I'm looking for the most efficient
way, am I incorrect to do so?)

Thanks,
rodchar

[Daniel]

Ah yes in that case code checks if it is blank, if so insert a null yep.
"rodchar" <ro*****@discussions.microsoft.comwrote in message
news:04**********************************@microsof t.com...

>i think that answers my question. The blank is for the dropdownlist so that
if the selection is blank it will store a null in the database. thanks,
rod.

"Daniel" wrote:

>What would a blank entry indicate?

I have never seen a need for a blank entry in a database. Not a good
idea.
(unless by blank you mean a null value?)
"rodchar" <ro*****@discussions.microsoft.comwrote in message
news:69**********************************@microso ft.com...

hey all,

i have a formview that contains a dropdownlist. it's datasource is
coming
from a table. the selectedValue can be blank. Would it better to add a
blank
in the database table or dynamically in the code-behind. And how many
routines would i need in either case? (I'm looking for the most
efficient
way, am I incorrect to do so?)

Thanks,
rodchar