Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.clipper.visual-objects > #8151

Re: Vo2Ado DBTYPE_DBTIME2 (145)

Message-ID <556D57B0.9060703@heliks.nl> (permalink)
Date 2015-06-02 09:13 +0200
Newsgroups comp.lang.clipper.visual-objects
From Robert van der Hulst <robert@heliks.nl>
Subject Re: Vo2Ado DBTYPE_DBTIME2 (145)
References <4dc5eb62-7e54-4043-8918-22da78c8abd1@googlegroups.com>

Show all headers | View raw


Veselin,

Vo2Ado does NOT look at the DBTYPE values, but uses the AdoField:Type 
property to determine how to convert the values.
It does this in the AdoServer:__AdoType2VOType() method, which you can 
override when needed.

I do not think that Vo2Ado is responsible for the Multi-step error. If 
it guesses the type incorrectly you will not have any errors, but you 
will get the incorrect data back.

I looked at the internet, and it seems that the DBTYPE_DBTIME2 type is 
not properly supported by the Ado library, so obviously Vo2Ado cannot 
support it as well.

Robert

> Vo 2.8 SP2 2830 Vo2Ado application access Sql Anywhere 16 DataBase. The SQL Anywhere 16 OLE DB provider now supports the DBTYPE_DBTIME2 data type. DBTYPE_DBTIME2 (145) is an OLE DB type that supports the TIME data type with fractional seconds.
> I want to ask whether Vo2Ado maintains this type (DBTYPE_DBTIME2) because Vo2Ado returns error : Multiple-step operation generated errors. Check each status value.
>
> Thanks.
>
> Veselin
> .
>


-- 
Robert van der Hulst
robert@heliks.nl

Back to comp.lang.clipper.visual-objects | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

Vo2Ado DBTYPE_DBTIME2 (145) office.sonita@gmail.com - 2015-06-01 08:41 -0700
  Re: Vo2Ado DBTYPE_DBTIME2 (145) Robert van der Hulst <robert@heliks.nl> - 2015-06-02 09:13 +0200
    Re: Vo2Ado DBTYPE_DBTIME2 (145) office.sonita@gmail.com - 2015-06-02 07:31 -0700
      Re: Vo2Ado DBTYPE_DBTIME2 (145) Robert van der Hulst <robert@heliks.nl> - 2015-06-03 10:01 +0200

csiph-web