Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.clipper.visual-objects > #8147 > unrolled thread
| Started by | office.sonita@gmail.com |
|---|---|
| First post | 2015-06-01 08:41 -0700 |
| Last post | 2015-06-03 10:01 +0200 |
| Articles | 4 — 2 participants |
Back to article view | Back to comp.lang.clipper.visual-objects
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
| From | office.sonita@gmail.com |
|---|---|
| Date | 2015-06-01 08:41 -0700 |
| Subject | Vo2Ado DBTYPE_DBTIME2 (145) |
| Message-ID | <4dc5eb62-7e54-4043-8918-22da78c8abd1@googlegroups.com> |
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
[toc] | [next] | [standalone]
| From | Robert van der Hulst <robert@heliks.nl> |
|---|---|
| Date | 2015-06-02 09:13 +0200 |
| Message-ID | <556D57B0.9060703@heliks.nl> |
| In reply to | #8147 |
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
[toc] | [prev] | [next] | [standalone]
| From | office.sonita@gmail.com |
|---|---|
| Date | 2015-06-02 07:31 -0700 |
| Message-ID | <3ed2b786-b893-4b9b-9814-372ec4979512@googlegroups.com> |
| In reply to | #8151 |
Robert, AdoField:Type returns 145 (which is correct for DBTYPE_DBTIME2), but AdoRecordset:FieldGet() or AdoRecordSet:GetRows() causes runtime error AdoErrors Class returns Provider = SAOLEDB.16 Description = Multiple-step operation generated errors. Check each status value. SQLState = '' NativeError = 0 SQLString = select f_date,t_datetime,t_time from dba._test t_time is a time data type field. As a workaround for now we changed SqlSelect ...string(t_time) as t_time, but if there is another solution would be better. Thanks Veselin
[toc] | [prev] | [next] | [standalone]
| From | Robert van der Hulst <robert@heliks.nl> |
|---|---|
| Date | 2015-06-03 10:01 +0200 |
| Message-ID | <556EB443.3060606@heliks.nl> |
| In reply to | #8155 |
Veselin, I am not sure why the type returns 145. That is not a valid value for the "DataTypeEnum". (see https://msdn.microsoft.com/en-us/library/windows/desktop/ms675318%28v=vs.85%29.aspx) This is probably the reason that you are getting errors. Robert > Robert, > > AdoField:Type returns 145 (which is correct for DBTYPE_DBTIME2), but AdoRecordset:FieldGet() or AdoRecordSet:GetRows() causes runtime error > > AdoErrors Class returns > > Provider = SAOLEDB.16 > Description = Multiple-step operation generated errors. Check each status value. > SQLState = '' > NativeError = 0 > SQLString = select f_date,t_datetime,t_time from dba._test > > t_time is a time data type field. > > As a workaround for now we changed SqlSelect ...string(t_time) as t_time, but if there is another solution would be better. > > Thanks > > Veselin > . > -- Robert van der Hulst robert@heliks.nl
[toc] | [prev] | [standalone]
Back to top | Article view | comp.lang.clipper.visual-objects
csiph-web