Hi,

We like the cursoradapter class a lot here:)

So we moved all our codebase from "remote views"
to cursoradapters. In a multiplatform c/s app that
can run ASA sybase or MS SQL server depending on
the customer's db size and personal taste...

Everything runs nicely except for TWO nasty bugs
in the implementation.

One is extremely difficult to catch and would only
happen in when actively opening and closing cursors
repeatingly. Only happens on ASA. It may be an
ASA odbc bug and we can leave with this one.

The other one is really much nastier and only
happens when loading big blobs (more than 8K)
into SQL server (carnation 2000). It won't affect
the Sybase ASA.

Blobs below 8K (jpeg pictures) > OK
Blobs over 8K (multip. tiff and thick jpeg)> No

8K... That looks like an implementation bug.

Curious and annoying. The only way we found
for data upload was to create a "good old"
remote view for blob upload... but that
bogs the whole cursoradapter concept down.

Has anyone else stumbled on this?

Has this bug been located and will it be
cured in the SP1? OR is is an ODBC bug
that only affects cursoradapter objects?

Franck