Don't mean to sound picky here Lion, but I am using
Dreamweaver's "Wizards"
to create the Update and Insert forms that don't work - I'm
not sure that
it's 100% my lack of understanding considering that I'm being
led down the
garden path a bit by DW. :o) What you're saying is that the
DW wizards
don't create the code correctly, right?
In all honesty, I just gave up on radio groups on my
Insert/Update forms
because I just couldn't get them to work using DW and I don't
have the ASP
knowledge to hand code it (which is why I bought DW). Next
time I'm doing
it, I'll have a crack at hand coding those bits.
I appreciate your advice, again. Thank you.
Regards
Nath.
"Lionstone" <HIDElionstone@HIDEhushmail.com> wrote in
message
news:ekho0p$nb8$1@forums.macromedia.com...
>
> "tradmusic.com" <sales@NOSHPAMtradmusic.com> wrote
in message
> news:ekh97p$5tr$1@forums.macromedia.com...
>> Had to ditch it and change to check boxes!
>> Radio groups - nightmare for an INSERT or UPDATE!
>>
>> Nath.
>
> Radio groups are easy for insert and update. Your
problem is a lack of
> understanding regarding your data types.
> NULL <> 0 and NULL <> 1, so when you have a
NULL value (which is also what
> caused your "invalid use of CStr" error), neither button
will be selected
> if you're checking for equality both times. If something
MUST be
> selected, then use = for the first test and <> for
the second. Also, the
> SQL Server BIT type needs no comparison - it is in
itself a true or false
> value.
>
> <%
> If myRS.Fields.Item("someBIT").Value Then
> %>
>
> etc.
>