The -=WEIRDEST=- bug with ASP/SQL/IIS (Micro$oft bug?)

Thread View: microsoft.public.inetserver.iis

3 messages

[T] Back to Threads [V] Tree View [G] Group Articles

3 total messages Started by Oz Ben Eliezer Thu, 29 Apr 1999 00:00

Author: Oz Ben Eliezer
Date: Thu, 29 Apr 1999 00:00

30 lines
2009 bytes

Hello.
I'm using IIS4, SQL 6.5, WinNT 4 Server.
I'm writing an ASP and stumbled upon the weirdest thing.
I'm accessing a recordset called RS. After one access to it (READ
access) - the value in the specific field I accessed, and sometimes
other fields in the recordset are CLEARED. Here's a code example:

<%
Response.Write("<BR> RS: " & RS("Field1") )
Response.Write("<BR> RS: " & RS("Field1") )
%>

Suppose the value in RS("Field1") is "hello". The HTML file will
display:

RS: hello
RS:

Because the value in RS("Field1") is cleared after the first access!
The same thing happens when I access RS("Field1") while copying the
value into a variable, while checking it with an IF statement...

If it ever happened to you and you know what I can do about it (I have a
few ideas how to WORK AROUND this thing, but I'd like to understand what
is going on here) then please tell me about it. If you can, EMAIL me
please.

Oz,
Netvision
obe@netvision.net.il

Re: The -=WEIRDEST=- bug with ASP/SQL/IIS (Micro$oft bug?)

Author: Aaron Bertrand
Date: Thu, 29 Apr 1999 00:00

28 lines
2029 bytes

If field1 is a text field, you'll want to (a) make sure that you ask for it
LAST in your SQL query (and don't use select * ...  syntax) and (b) assign
it to a variable right after your set recordset line.  See the link in my
signature for more details.

--
   _______________________________________________________
   aaron bertrand [active server pages mvp]
   http://www.swynk.com/friends/bertrand/

   Are we at a point where kindergarten children are going
   to have to go through a metal detector before returning
   from their recess or lunch break?
   _______________________________________________________



> Hello.
> I'm using IIS4, SQL 6.5, WinNT 4 Server.
> I'm writing an ASP and stumbled upon the weirdest thing.
> I'm accessing a recordset called RS. After one access to it (READ
> access) - the value in the specific field I accessed, and sometimes
> other fields in the recordset are CLEARED. Here's a code example:
>
> <%
> Response.Write("<BR> RS: " & RS("Field1") )
> Response.Write("<BR> RS: " & RS("Field1") )
> %>

Re: The -=WEIRDEST=- bug with ASP/SQL/IIS (Micro$oft bug?)

Author: Oz Ben Eliezer
Date: Sun, 02 May 1999 00:00

34 lines
2404 bytes

I'd like to get more information about it (does it appear in Micro$oft KB?) but
the link doesn't work!

Thanks, Oz

Aaron Bertrand wrote:

> If field1 is a text field, you'll want to (a) make sure that you ask for it
> LAST in your SQL query (and don't use select * ...  syntax) and (b) assign
> it to a variable right after your set recordset line.  See the link in my
> signature for more details.
>
> --
>    _______________________________________________________
>    aaron bertrand [active server pages mvp]
>    http://www.swynk.com/friends/bertrand/
>
>    Are we at a point where kindergarten children are going
>    to have to go through a metal detector before returning
>    from their recess or lunch break?
>    _______________________________________________________
>
> > Hello.
> > I'm using IIS4, SQL 6.5, WinNT 4 Server.
> > I'm writing an ASP and stumbled upon the weirdest thing.
> > I'm accessing a recordset called RS. After one access to it (READ
> > access) - the value in the specific field I accessed, and sometimes
> > other fields in the recordset are CLEARED. Here's a code example:
> >
> > <%
> > Response.Write("<BR> RS: " & RS("Field1") )
> > Response.Write("<BR> RS: " & RS("Field1") )
> > %>

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads