(John Vannoy)
12/25/2002 8:50:00 PM
Sarah,
No solution yet. I figure it's a bug in ODBC.NET. Workaround is to
write a VB6 COM component, access the data via ADO 2.7, and pass back
a 2D array to your VB.net code. Hey, it works, and it encapsulates
the workaround code. When ODBC.NET eventually is fixed, it will be
easy to drop in.
John
"Sarah Aldridge" <msdn@protocol.co.uk> wrote in message news:<356b01c25ffc$f6baa6a0$3bef2ecf@TKMSFTNGXA10>...
> Hi,
>
> I am having exactly the same problem as you with ODBC.NET
> Truncating the text values in my fields to 200 bytes.
>
> I have also tried connecting in VB.Net using ADO ver 2.7
> and the same DSN and that works fine with no truncation.
>
> Can anyone help further.
>
> Thanks
>
> Sarah
>
> >-----Original Message-----
> >I'm using ODBC.Net to connect to a Lotus Notes r5
> database.
> >Everything works great, except one minor detail - it
> truncates text
> >fields to 200 bytes! This is a major hold up, as some
> fields contain
> >up to 900 bytes.
> >
> >I am using the Notes 3.01 ODBC driver. I have created a
> DSN and set
> >the "max length of text fields" property to 1500. I also
> set the "max
> >length of rich text fields" to 1500.
> >
> >If I connect thru this same DSN using VB6 and ADO, I
> experience no
> >truncation.
> >
> >Why would it truncate text fields to 200 bytes? How can
> I get around
> >this?
> >
> >Thanks,
> >John
> >.
> >