Sybase ADO driver having problems with long strings and null



We are in the process of switching our sybase clients. Currently we
are using an older Sybase client. It has the older datadirect ADO
provider (Sybase.ASEOLEDBProvider). My current code handles
Varchar(255) and Text fields and nulls without any problems using the
standard Delphi 7.0 ADO components.

When I am testing with the new client uses Sybase's ADO provider
(ASEOLEDB). My code loads fine in reading the data. When I try to
update a large Varchar or Text field I get the following error.

"Multiple-step OLE DB operation generated error. Check each DB status
value, if available. No work was done"

When a field is nulled out by setting the parameter to Null, I get the
following error.

"Data overflow. Increase specified column size or buffer size."

If I remove the large string fields from the query, everything works.

1) I do set the datatypes (in the case of strings it is ftString)
2) If the field is null, I assign "Null" to the val of the parameter
.



Relevant Pages

  • Sybase ADO driver having problems with long strings and null
    ... We are in the process of switching our sybase clients. ... It has the older datadirect ADO ... When I am testing with the new client uses Sybase's ADO provider ... If I remove the large string fields from the query, ...
    (borland.public.delphi.database.ado)
  • Re: Sybase ADO driver having problems with long strings and null
    ... It has the older datadirect ADO ... When I am testing with the new client uses Sybase's ADO provider ... If I remove the large string fields from the query, ... We have decided to use the old sybase client for now until the the client becomes more mature ...
    (borland.public.delphi.database.ado)
  • Re: Why not use DAO?
    ... You have been refering to DAO vs. ADO when these two things (in the context ... you must have ALREADY used a provider to get to. ... interface for working with JET databases. ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Why not use DAO?
    ... All reall life programmers i know of use the jet oledb 3.5 or 4.0 provider ... ADO for ACCESS ... The TS asked "Why not used DAO ?" ... interface for working with JET databases. ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Regarding fastest database interaction with Oracle in VC++
    ... If you are using ADO, then you will have a Connection object. ... is a lightweight COM API that sits on top of OLEDB. ... If you install MDAC 2.8, it will install some providers for you. ... It will install the MS Oracle provider. ...
    (microsoft.public.vc.database)