Very strange problem!

Seth Weathers

unread,

Jun 15, 2002, 5:06:10 PM6/15/02

to

That did it! You saved the day! Too bad I didn't ask before I pulled all my
hair out!:)

What causes that?

Thanks!
Seth

"Joris van Lier" <whi...@hotmail.com> wrote in message
news:aefvlo$8jn$1...@forums.macromedia.com...
> Use a ClientSide Cursor
>
> Click your recordset in the *server behaviors*-panle and select the cursor
> location from the property-inspector
>
> Joris van Lier
>
>

Seth Weathers

unread,

Jun 15, 2002, 5:01:12 PM6/15/02

to

Hi,

I've got a table that I'm pulling data from. I can pull all the data except
for a particular column. The column is a memo field (i don't think it makes
a difference). All the othere data comes out fine... the one column just
shows up blank on the page.

I've double checked my database and the data is there.

What can be the problem? I've never had anything like this happen!

Thanks!
Seth

Joris van Lier

unread,

Jun 15, 2002, 2:05:26 PM6/15/02

to

Joris van Lier

unread,

Jun 15, 2002, 2:19:42 PM6/15/02

to

This is what i understand about lockTypes and cursors.: a ReadOnly
Cursortype does not establish locks on a record, a lock is to ensure that
the data cannot be changed while you're working with it, other
DatabaseClients are put in a queue till the record is unlocked, so this can
have a significant impact on performance problems.
The standard Ultradev recordset cursor / lock settings will establish locks
on the records, and ms Access can't handle too many of them.
I've experienced that when Ultradev/Access applications err out with "Too
many Client Tasks"; changing the LockType will increase the number of
clients access can handle.

About CursorLocation: the msSQL Text/Image(blob) type,
this fieldtype can hold VERY large amounts of data (up to 2 GB
maybe more). Since the datablocks can be so large, the databaseserver wil
send it BLIND, i'e it wil start sending the data without knowing where the
end is. This is where the trouble starts, but i don't know why. On the other
hand, if you set the cursortype to ClientSide, the database-server (Oracle)
will turn over all the data to the client (the Webserver, actually ODBC or
ADODB) and let the client handle the data itself, since the client has
allready retrieved ALL the data, it already knows where the end of the
datablob is, and can handle the data okay.

Allso, Microsoft advices to place all BLOB-type columns at the end of your
select list
i.e. SELECT intNumber, vcharName, blobField, blobField2 FROM tblMyTable
as opposed to SELECT intNumber, blobField, charName, blobField2 FROM
tblMyTable

<quote>
MS: http://support.microsoft.com/support/kb/articles/q175/2/39.asp

ActiveX Data Objects (ADO), versions 1.0, 1.5, 2.0, 2.1, 2.1 SP1

When dealing with BLOB fields from Microsoft SQL Server, you must put them
to the right of non-BLOB columns in the resultset. To be safe, you should
also read the columns in left-to-right order, so if you have two BLOB
columns as the last two columns in your resultset, read the first one and
then the second. Do not read them in the reverse order.

</quote>

Furthermore the following sometimes doesn't work
<% If (recset.fields.item("blobField").Value <> "") Then
Response.Write(recset.fields.item("blobField").Value)
End If %>

you should first assign it to a variable and use that var instead.

<%
Dim blobData
blobData = recset.fields.item("blobField").Value
If (blobData <> "") Then
Response.Write(blobData)
End If
%>

This was driving me nuts...
Joris van Lier

Seth Weathers

unread,

Jun 15, 2002, 5:20:19 PM6/15/02

to

WOW! I wasn't expecting that much of a detailed explaination:)

Thanks... it has furthererd my limited knowledge:)

I never know anything about that until now!

Seth

"Joris van Lier" <whi...@hotmail.com> wrote in message

news:aeg0gg$9jv$1...@forums.macromedia.com...

Thierry Koblentz

unread,

Jun 15, 2002, 5:55:18 PM6/15/02

to

Hi Joris,
Thanks for your post!

Thierry

"Joris van Lier" <whi...@hotmail.com> wrote in message

news:aeg0gg$9jv$1...@forums.macromedia.com...