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


Groups > comp.lang.clipper.visual-objects > #7779 > unrolled thread

Precision in SQL

Started byJames Martin <james@northwoodlumber.com>
First post2015-02-24 10:47 -0500
Last post2015-02-26 13:35 -0600
Articles 20 on this page of 21 — 6 participants

Back to article view | Back to comp.lang.clipper.visual-objects


Contents

  Precision in SQL James Martin <james@northwoodlumber.com> - 2015-02-24 10:47 -0500
    Re: Precision in SQL James Martin <james@northwoodlumber.com> - 2015-02-24 15:17 -0500
    Re: Precision in SQL "Willie Moore" <williem@wmconsulting.com> - 2015-02-24 14:55 -0600
      Re: Precision in SQL James Martin <james@northwoodlumber.com> - 2015-02-24 16:15 -0500
      Re: Precision in SQL James Martin <james@northwoodlumber.com> - 2015-02-24 16:35 -0500
        Re: Precision in SQL Karl Faller <mail_withoutthat_@_drei-f_andthat_.de> - 2015-02-24 22:49 +0100
          Re: Precision in SQL James Martin <james@northwoodlumber.com> - 2015-02-24 18:11 -0500
            Re: Precision in SQL Malcolm G <malcolm-news2012delete@delete.jobstream.com> - 2015-02-25 10:03 +0000
              Re: Precision in SQL dlzc <dlzc1@cox.net> - 2015-02-25 06:44 -0800
                Re: Precision in SQL James Martin <james@northwoodlumber.com> - 2015-02-25 12:08 -0500
                  Re: Precision in SQL Malcolm G <malcolm-news2012delete@delete.jobstream.com> - 2015-02-26 09:32 +0000
                    Re: Precision in SQL James Martin <james@northwoodlumber.com> - 2015-02-26 08:11 -0500
                      Re: Precision in SQL Malcolm G <malcolm-news2012delete@delete.jobstream.com> - 2015-02-26 13:31 +0000
                        Re: Precision in SQL James Martin <james@northwoodlumber.com> - 2015-02-26 09:39 -0500
                        Re: Precision in SQL James Martin <james@northwoodlumber.com> - 2015-02-26 11:59 -0500
                          Re: Precision in SQL Frans Wauters <info@wautersit.com> - 2015-02-26 15:25 -0800
                Re: Precision in SQL James Martin <james@northwoodlumber.com> - 2015-02-25 13:13 -0500
                Re: Precision in SQL James Martin <james@northwoodlumber.com> - 2015-02-25 16:15 -0500
                  Re: Precision in SQL Karl Faller <mail_withoutthat_@_drei-f_andthat_.de> - 2015-02-25 23:08 +0100
                    Re: Precision in SQL James Martin <james@northwoodlumber.com> - 2015-02-26 08:18 -0500
                  Re: Precision in SQL "Willie Moore" <williem@wmconsulting.com> - 2015-02-26 13:35 -0600

Page 1 of 2  [1] 2  Next page →


#7779 — Precision in SQL

FromJames Martin <james@northwoodlumber.com>
Date2015-02-24 10:47 -0500
SubjectPrecision in SQL
Message-ID<mci656$2bq$1@dont-email.me>
Can someone give me a quick answer? When browsing a SQL database with 
bBrowser and Adoserver, all the numbers are rounded to the nearest whole 
number instead of the required decimal points. They are correct in the 
database, and I put populated the database from a DBF using SQL commands 
via the Adoconnection. Somewhere in the retrieval the decimal portion is 
lost. I have initialized the Adoservers myself, and I tried to use 
SetDataField()

Thanks.

James

[toc] | [next] | [standalone]


#7784

FromJames Martin <james@northwoodlumber.com>
Date2015-02-24 15:17 -0500
Message-ID<mcilv1$8r4$1@dont-email.me>
In reply to#7779
I have used the ADO server editor to create the server, with the same 
result.

James

On 15-02-24 10:47 AM, James Martin wrote:
> Can someone give me a quick answer? When browsing a SQL database with
> bBrowser and Adoserver, all the numbers are rounded to the nearest whole
> number instead of the required decimal points. They are correct in the
> database, and I put populated the database from a DBF using SQL commands
> via the Adoconnection. Somewhere in the retrieval the decimal portion is
> lost. I have initialized the Adoservers myself, and I tried to use
> SetDataField()
>
> Thanks.
>
> James

[toc] | [prev] | [next] | [standalone]


#7785

From"Willie Moore" <williem@wmconsulting.com>
Date2015-02-24 14:55 -0600
Message-ID<mciofd$1dq$1@speranza.aioe.org>
In reply to#7779
James,

It has been a long time since I have used ADOServer. Have you tried a simple 
console app first to make sure what the ADOServer is returning. I believe 
that there is a sample included in VO2ADO that you can modify to just print 
out the contents of a table.

Regards,
Willie
Vulcan VIP

"James Martin"  wrote in message news:mci656$2bq$1@dont-email.me...

Can someone give me a quick answer? When browsing a SQL database with
bBrowser and Adoserver, all the numbers are rounded to the nearest whole
number instead of the required decimal points. They are correct in the
database, and I put populated the database from a DBF using SQL commands
via the Adoconnection. Somewhere in the retrieval the decimal portion is
lost. I have initialized the Adoservers myself, and I tried to use
SetDataField()

Thanks.

James 

[toc] | [prev] | [next] | [standalone]


#7786

FromJames Martin <james@northwoodlumber.com>
Date2015-02-24 16:15 -0500
Message-ID<mcipcr$oag$1@dont-email.me>
In reply to#7785
Thanks for that answer. It is just the numerics that are a problem.

I will check and get back.

James

On 15-02-24 03:55 PM, Willie Moore wrote:
> James,
>
> It has been a long time since I have used ADOServer. Have you tried a
> simple console app first to make sure what the ADOServer is returning. I
> believe that there is a sample included in VO2ADO that you can modify to
> just print out the contents of a table.
>
> Regards,
> Willie
> Vulcan VIP
>
> "James Martin"  wrote in message news:mci656$2bq$1@dont-email.me...
>
> Can someone give me a quick answer? When browsing a SQL database with
> bBrowser and Adoserver, all the numbers are rounded to the nearest whole
> number instead of the required decimal points. They are correct in the
> database, and I put populated the database from a DBF using SQL commands
> via the Adoconnection. Somewhere in the retrieval the decimal portion is
> lost. I have initialized the Adoservers myself, and I tried to use
> SetDataField()
>
> Thanks.
>
> James

[toc] | [prev] | [next] | [standalone]


#7787

FromJames Martin <james@northwoodlumber.com>
Date2015-02-24 16:35 -0500
Message-ID<mciqii$tg2$1@dont-email.me>
In reply to#7785
Tried the sample just as it was given. Same problem. For example 199.86 
comes on the browser as 199.00 And when I read the field into an SLE it 
is also without the decimal.

I guess the number could be stored as a string, and converted back to a 
numeric when read from the database. I'm wondering if this is a common 
problem or if there is a switch somewhere to change this behaviour.

James

On 15-02-24 03:55 PM, Willie Moore wrote:
> James,
>
> It has been a long time since I have used ADOServer. Have you tried a
> simple console app first to make sure what the ADOServer is returning. I
> believe that there is a sample included in VO2ADO that you can modify to
> just print out the contents of a table.
>
> Regards,
> Willie
> Vulcan VIP
>
> "James Martin"  wrote in message news:mci656$2bq$1@dont-email.me...
>
> Can someone give me a quick answer? When browsing a SQL database with
> bBrowser and Adoserver, all the numbers are rounded to the nearest whole
> number instead of the required decimal points. They are correct in the
> database, and I put populated the database from a DBF using SQL commands
> via the Adoconnection. Somewhere in the retrieval the decimal portion is
> lost. I have initialized the Adoservers myself, and I tried to use
> SetDataField()
>
> Thanks.
>
> James

[toc] | [prev] | [next] | [standalone]


#7788

FromKarl Faller <mail_withoutthat_@_drei-f_andthat_.de>
Date2015-02-24 22:49 +0100
Message-ID<acspea1t0bkmvv0msbv1bmpl4oq9e2d0uc@4ax.com>
In reply to#7787
James,
imho you are not clear re the error: 
Do you get a whole number "199"  or a "199.00" ?

Karl

>Tried the sample just as it was given. Same problem. For example 199.86 
>comes on the browser as 199.00 And when I read the field into an SLE it 
>is also without the decimal.
>
>I guess the number could be stored as a string, and converted back to a 
>numeric when read from the database. I'm wondering if this is a common 
>problem or if there is a switch somewhere to change this behaviour.
>
>James
>
>On 15-02-24 03:55 PM, Willie Moore wrote:
>> James,
>>
>> It has been a long time since I have used ADOServer. Have you tried a
>> simple console app first to make sure what the ADOServer is returning. I
>> believe that there is a sample included in VO2ADO that you can modify to
>> just print out the contents of a table.
>>
>> Regards,
>> Willie
>> Vulcan VIP
>>
>> "James Martin"  wrote in message news:mci656$2bq$1@dont-email.me...
>>
>> Can someone give me a quick answer? When browsing a SQL database with
>> bBrowser and Adoserver, all the numbers are rounded to the nearest whole
>> number instead of the required decimal points. They are correct in the
>> database, and I put populated the database from a DBF using SQL commands
>> via the Adoconnection. Somewhere in the retrieval the decimal portion is
>> lost. I have initialized the Adoservers myself, and I tried to use
>> SetDataField()
>>
>> Thanks.
>>
>> James

[toc] | [prev] | [next] | [standalone]


#7789

FromJames Martin <james@northwoodlumber.com>
Date2015-02-24 18:11 -0500
Message-ID<mcj054$nm6$1@dont-email.me>
In reply to#7788
Depending on the formatting in bBrowser I get 199.00 or 199. But the 
AdoServer data is 199

James

On 15-02-24 04:49 PM, Karl Faller wrote:
> James,
> imho you are not clear re the error:
> Do you get a whole number "199"  or a "199.00" ?
>
> Karl
>
>> Tried the sample just as it was given. Same problem. For example 199.86
>> comes on the browser as 199.00 And when I read the field into an SLE it
>> is also without the decimal.
>>
>> I guess the number could be stored as a string, and converted back to a
>> numeric when read from the database. I'm wondering if this is a common
>> problem or if there is a switch somewhere to change this behaviour.
>>
>> James
>>
>> On 15-02-24 03:55 PM, Willie Moore wrote:
>>> James,
>>>
>>> It has been a long time since I have used ADOServer. Have you tried a
>>> simple console app first to make sure what the ADOServer is returning. I
>>> believe that there is a sample included in VO2ADO that you can modify to
>>> just print out the contents of a table.
>>>
>>> Regards,
>>> Willie
>>> Vulcan VIP
>>>
>>> "James Martin"  wrote in message news:mci656$2bq$1@dont-email.me...
>>>
>>> Can someone give me a quick answer? When browsing a SQL database with
>>> bBrowser and Adoserver, all the numbers are rounded to the nearest whole
>>> number instead of the required decimal points. They are correct in the
>>> database, and I put populated the database from a DBF using SQL commands
>>> via the Adoconnection. Somewhere in the retrieval the decimal portion is
>>> lost. I have initialized the Adoservers myself, and I tried to use
>>> SetDataField()
>>>
>>> Thanks.
>>>
>>> James

[toc] | [prev] | [next] | [standalone]


#7790

FromMalcolm G <malcolm-news2012delete@delete.jobstream.com>
Date2015-02-25 10:03 +0000
Message-ID<R5hHw.131581$C91.89107@fx22.am4>
In reply to#7789
On 24/02/2015 23:11, James Martin wrote:
> Depending on the formatting in bBrowser I get 199.00 or 199. But the 
> AdoServer data is 199

Sounds odd.

I don't recognise the problem, but don't use ADOServer.

What I would do with those symptoms

1) look at the value of floatformat(uvalue,18,4) in case there is
something odd happening with the display code.

2) Look at the table/view definition to see what the column type is.
float or numeric(10,2) etc

3) Say what version of VO I was testing with

[toc] | [prev] | [next] | [standalone]


#7792

Fromdlzc <dlzc1@cox.net>
Date2015-02-25 06:44 -0800
Message-ID<6c2bab78-268c-4ff9-acd7-848ba040b966@googlegroups.com>
In reply to#7790
To the Group:

On Wednesday, February 25, 2015 at 3:03:30 AM UTC-7, Malcolm G wrote:
> On 24/02/2015 23:11, James Martin wrote:
> > Depending on the formatting in bBrowser I get
> > 199.00 or 199. But the AdoServer data is 199
> 
> Sounds odd.
> 
> I don't recognise the problem, but don't use
> ADOServer.
> 
> What I would do with those symptoms
> 
> 1) look at the value of floatformat(uvalue,18,4)
> in case there is something odd happening with
> the display code.
> 
> 2) Look at the table/view definition to see what
> the column type is. float or numeric(10,2) etc
> 
> 3) Say what version of VO I was testing with

Does VO have the equivalent of SET DECIMALS?

Does AdoServer configure itself automatically off data format, or does it require initialization via "pictures" or similar?

Is AdoServer a complied, standalone application, or a linked library?  In either case, it might be hard to reveal what needs to be revealed.

No response to me required... clearly.

David A. Smith

[toc] | [prev] | [next] | [standalone]


#7794

FromJames Martin <james@northwoodlumber.com>
Date2015-02-25 12:08 -0500
Message-ID<mckv9u$7hv$1@dont-email.me>
In reply to#7792
On 15-02-25 09:44 AM, dlzc wrote:
Using ODBC the decimals come through properly. Now I will try VO2ADO via 
the ODBC connection, and see if that works. The database is Postgresql, 
and I have tried the fields definition: Numeric(12,2) and Money, with no 
difference. VO does have a "SET DECIMALS" but that defaults to 2, and 
throught-out the application decimals are showing correctly. The version 
of VO is 2.8 sp2.

Incidently, with exactly the same code, only the database different, ADO 
displays no decimals, but ODBC does.

The problem with ODBC is that with it I am having problems with the ODBC 
connection in the various users of the terminal services.

James

> To the Group:
>
> On Wednesday, February 25, 2015 at 3:03:30 AM UTC-7, Malcolm G wrote:
>> On 24/02/2015 23:11, James Martin wrote:
>>> Depending on the formatting in bBrowser I get
>>> 199.00 or 199. But the AdoServer data is 199
>>
>> Sounds odd.
>>
>> I don't recognise the problem, but don't use
>> ADOServer.
>>
>> What I would do with those symptoms
>>
>> 1) look at the value of floatformat(uvalue,18,4)
>> in case there is something odd happening with
>> the display code.
>>
>> 2) Look at the table/view definition to see what
>> the column type is. float or numeric(10,2) etc
>>
>> 3) Say what version of VO I was testing with
>
> Does VO have the equivalent of SET DECIMALS?
>
> Does AdoServer configure itself automatically off data format, or does it require initialization via "pictures" or similar?
>
> Is AdoServer a complied, standalone application, or a linked library?  In either case, it might be hard to reveal what needs to be revealed.
>
> No response to me required... clearly.
>
> David A. Smith
>

[toc] | [prev] | [next] | [standalone]


#7799

FromMalcolm G <malcolm-news2012delete@delete.jobstream.com>
Date2015-02-26 09:32 +0000
Message-ID<2LBHw.869553$fp4.122640@fx10.am4>
In reply to#7794
On 25/02/2015 17:08, James Martin wrote:
> On 15-02-25 09:44 AM, dlzc wrote:
> Using ODBC the decimals come through properly. Now I will try VO2ADO via 
> the ODBC connection, and see if that works. The database is Postgresql, 
> and I have tried the fields definition: Numeric(12,2) and Money, with no 
> difference. VO does have a "SET DECIMALS" but that defaults to 2, and 
> throught-out the application decimals are showing correctly. The version 
> of VO is 2.8 sp2.
> 
> Incidently, with exactly the same code, only the database different, ADO 
> displays no decimals, but ODBC does.
> 
> The problem with ODBC is that with it I am having problems with the ODBC 
> connection in the various users of the terminal services.

Does Postgresql have a choice of ADO drivers?

My gut reaction would be that the ADO driver is reporting a datatype
that vo2ado treats as an integer. I would look at asking the ado layer
what data type it is reporting returned from the driver.

[toc] | [prev] | [next] | [standalone]


#7800

FromJames Martin <james@northwoodlumber.com>
Date2015-02-26 08:11 -0500
Message-ID<mcn5o7$vv1$1@dont-email.me>
In reply to#7799
This is my gut feeling too.

Since ODBC is not working right in our server configuration (we use 
AADServer) I will store all my numerics as Characters, have Accesses and 
Assigns to do the conversions. At least until I find answers.

I wouldn't know how to "ask the ado layer". The Postgresql ADO driver is 
no longer being actively developed, so it is a real candidate for being 
the culprit.

James

On 15-02-26 04:32 AM, Malcolm G wrote:
> On 25/02/2015 17:08, James Martin wrote:
>> On 15-02-25 09:44 AM, dlzc wrote:
>> Using ODBC the decimals come through properly. Now I will try VO2ADO via
>> the ODBC connection, and see if that works. The database is Postgresql,
>> and I have tried the fields definition: Numeric(12,2) and Money, with no
>> difference. VO does have a "SET DECIMALS" but that defaults to 2, and
>> throught-out the application decimals are showing correctly. The version
>> of VO is 2.8 sp2.
>>
>> Incidently, with exactly the same code, only the database different, ADO
>> displays no decimals, but ODBC does.
>>
>> The problem with ODBC is that with it I am having problems with the ODBC
>> connection in the various users of the terminal services.
>
> Does Postgresql have a choice of ADO drivers?
>
> My gut reaction would be that the ADO driver is reporting a datatype
> that vo2ado treats as an integer. I would look at asking the ado layer
> what data type it is reporting returned from the driver.
>

[toc] | [prev] | [next] | [standalone]


#7802

FromMalcolm G <malcolm-news2012delete@delete.jobstream.com>
Date2015-02-26 13:31 +0000
Message-ID<veFHw.947870$Fr6.85385@fx14.am4>
In reply to#7800
On 26/02/2015 13:11, James Martin wrote:
> This is my gut feeling too.
> 
> Since ODBC is not working right in our server configuration (we use 
> AADServer) I will store all my numerics as Characters, have Accesses and 
> Assigns to do the conversions. At least until I find answers.
> 
> I wouldn't know how to "ask the ado layer". The Postgresql ADO driver is 
> no longer being actively developed, so it is a real candidate for being 
> the culprit.

We have some slightly specialist code but if you want to give it a go

We start with an ADORecordSet
the :Fields access gets you a collection of fields
oField:=oFields[nField]
will get you one of the fields by position
oField:type gives you the adotype (e.g. adDate which is 7)
and oField:Name the name

[toc] | [prev] | [next] | [standalone]


#7803

FromJames Martin <james@northwoodlumber.com>
Date2015-02-26 09:39 -0500
Message-ID<mcnatl$k5g$1@dont-email.me>
In reply to#7802
OK, I'll check this. Thanks.

James

On 15-02-26 08:31 AM, Malcolm G wrote:
> On 26/02/2015 13:11, James Martin wrote:
>> This is my gut feeling too.
>>
>> Since ODBC is not working right in our server configuration (we use
>> AADServer) I will store all my numerics as Characters, have Accesses and
>> Assigns to do the conversions. At least until I find answers.
>>
>> I wouldn't know how to "ask the ado layer". The Postgresql ADO driver is
>> no longer being actively developed, so it is a real candidate for being
>> the culprit.
>
> We have some slightly specialist code but if you want to give it a go
>
> We start with an ADORecordSet
> the :Fields access gets you a collection of fields
> oField:=oFields[nField]
> will get you one of the fields by position
> oField:type gives you the adotype (e.g. adDate which is 7)
> and oField:Name the name
>
>

[toc] | [prev] | [next] | [standalone]


#7804

FromJames Martin <james@northwoodlumber.com>
Date2015-02-26 11:59 -0500
Message-ID<mcnj3q$nci$1@dont-email.me>
In reply to#7802
OK using AdoRecordSet As an example I get the following on a fields:
Actualsize: 19
Definedsize: -1
Name: stotal
Numericscale: 0
Precision: 39
Type: 131
Value: 559.00

The field in the database data manager is Numeric(12,2) and the value is 
559.20

So there are errors already in the RecordSet. I kind of suspected that.

James



On 15-02-26 08:31 AM, Malcolm G wrote:
> On 26/02/2015 13:11, James Martin wrote:
>> This is my gut feeling too.
>>
>> Since ODBC is not working right in our server configuration (we use
>> AADServer) I will store all my numerics as Characters, have Accesses and
>> Assigns to do the conversions. At least until I find answers.
>>
>> I wouldn't know how to "ask the ado layer". The Postgresql ADO driver is
>> no longer being actively developed, so it is a real candidate for being
>> the culprit.
>
> We have some slightly specialist code but if you want to give it a go
>
> We start with an ADORecordSet
> the :Fields access gets you a collection of fields
> oField:=oFields[nField]
> will get you one of the fields by position
> oField:type gives you the adotype (e.g. adDate which is 7)
> and oField:Name the name
>
>

[toc] | [prev] | [next] | [standalone]


#7808

FromFrans Wauters <info@wautersit.com>
Date2015-02-26 15:25 -0800
Message-ID<3f9d8ab7-89f6-4872-a87b-945a311e1c98@googlegroups.com>
In reply to#7804
Hi,

Read the NG at https://groups.google.com/forum/?hl=nl#!searchin/comp.lang.clipper.visual-objects/frans$20wauters%7Csort:date/comp.lang.clipper.visual-objects/3Gs9yQcZLo8/wNBFCeczwA0J

Robert van de Hulst :
.../...
The problem seems to be that the date column type did not exist when Vo2Ado was created. We simply missed the right conversion in our code. And we cannot use the schema information like you did in your code, because that would not work for other OLEDB providers.
.../...

So (VO2)ADO is not an "exact" science as it must cover the great common database denominator and possible bugs in underlying drivers are chasing yours.

To tackle some things, I read the systemtables from the MS SQL database in an array at the start of my program and matched this in VO code. See SQL_TabelStruct( oConn AS OBJECT, cTableName AS STRING ) somewhere in the dialog in the newsgroup.

Regards,
Frans

[toc] | [prev] | [next] | [standalone]


#7795

FromJames Martin <james@northwoodlumber.com>
Date2015-02-25 13:13 -0500
Message-ID<mcl334$odb$1@dont-email.me>
In reply to#7792
ADO via ODBC acts exactly like ADO direct. Is there some incompatibility 
in ADO and what the data drivers give out?

James

On 15-02-25 09:44 AM, dlzc wrote:
> To the Group:
>
> On Wednesday, February 25, 2015 at 3:03:30 AM UTC-7, Malcolm G wrote:
>> On 24/02/2015 23:11, James Martin wrote:
>>> Depending on the formatting in bBrowser I get
>>> 199.00 or 199. But the AdoServer data is 199
>>
>> Sounds odd.
>>
>> I don't recognise the problem, but don't use
>> ADOServer.
>>
>> What I would do with those symptoms
>>
>> 1) look at the value of floatformat(uvalue,18,4)
>> in case there is something odd happening with
>> the display code.
>>
>> 2) Look at the table/view definition to see what
>> the column type is. float or numeric(10,2) etc
>>
>> 3) Say what version of VO I was testing with
>
> Does VO have the equivalent of SET DECIMALS?
>
> Does AdoServer configure itself automatically off data format, or does it require initialization via "pictures" or similar?
>
> Is AdoServer a complied, standalone application, or a linked library?  In either case, it might be hard to reveal what needs to be revealed.
>
> No response to me required... clearly.
>
> David A. Smith
>

[toc] | [prev] | [next] | [standalone]


#7797

FromJames Martin <james@northwoodlumber.com>
Date2015-02-25 16:15 -0500
Message-ID<mcldo3$9d5$1@dont-email.me>
In reply to#7792
Well it seems to come down to major changes:

1.- Use ADO and change all my numeric fields to character and convert 
data as it goes and comes from the database.

2.- Get ODBC going. It works well on the terminal login I program in, 
but in any other terminal I can't get ODBC to work, even if it is 
configured the same. Does anyone have ideas as to what could keep ODBC 
from working on other terminal logins?

James

On 15-02-25 09:44 AM, dlzc wrote:
> To the Group:
>
> On Wednesday, February 25, 2015 at 3:03:30 AM UTC-7, Malcolm G wrote:
>> On 24/02/2015 23:11, James Martin wrote:
>>> Depending on the formatting in bBrowser I get
>>> 199.00 or 199. But the AdoServer data is 199
>>
>> Sounds odd.
>>
>> I don't recognise the problem, but don't use
>> ADOServer.
>>
>> What I would do with those symptoms
>>
>> 1) look at the value of floatformat(uvalue,18,4)
>> in case there is something odd happening with
>> the display code.
>>
>> 2) Look at the table/view definition to see what
>> the column type is. float or numeric(10,2) etc
>>
>> 3) Say what version of VO I was testing with
>
> Does VO have the equivalent of SET DECIMALS?
>
> Does AdoServer configure itself automatically off data format, or does it require initialization via "pictures" or similar?
>
> Is AdoServer a complied, standalone application, or a linked library?  In either case, it might be hard to reveal what needs to be revealed.
>
> No response to me required... clearly.
>
> David A. Smith
>

[toc] | [prev] | [next] | [standalone]


#7798

FromKarl Faller <mail_withoutthat_@_drei-f_andthat_.de>
Date2015-02-25 23:08 +0100
Message-ID<schsea5c3bncdl0qer2phdgd9k3760kji2@4ax.com>
In reply to#7797
James,
>Well it seems to come down to major changes:
>
>1.- Use ADO and change all my numeric fields to character and convert 
>data as it goes and comes from the database.
I know nothing about AdoServer, but i can't imagine, that it's not
able to correctly read numerics. BTW, presume you  talk about Vo2Ado?
If the latter, you could contact Robert, but unfortunately for you
he's just gone on a 2 month tour on the southern hemisphere ;-(

The next thing i would try is use the Server NOT with bBrowser, but
with a regular datawindow. If you see the same, bBrowser is faultless,
if not, you might contact Joachim...

Karl

>2.- Get ODBC going. It works well on the terminal login I program in, 
>but in any other terminal I can't get ODBC to work, even if it is 
>configured the same. Does anyone have ideas as to what could keep ODBC 
>from working on other terminal logins?
>
>James
>
>On 15-02-25 09:44 AM, dlzc wrote:
>> To the Group:
>>
>> On Wednesday, February 25, 2015 at 3:03:30 AM UTC-7, Malcolm G wrote:
>>> On 24/02/2015 23:11, James Martin wrote:
>>>> Depending on the formatting in bBrowser I get
>>>> 199.00 or 199. But the AdoServer data is 199
>>>
>>> Sounds odd.
>>>
>>> I don't recognise the problem, but don't use
>>> ADOServer.
>>>
>>> What I would do with those symptoms
>>>
>>> 1) look at the value of floatformat(uvalue,18,4)
>>> in case there is something odd happening with
>>> the display code.
>>>
>>> 2) Look at the table/view definition to see what
>>> the column type is. float or numeric(10,2) etc
>>>
>>> 3) Say what version of VO I was testing with
>>
>> Does VO have the equivalent of SET DECIMALS?
>>
>> Does AdoServer configure itself automatically off data format, or does it require initialization via "pictures" or similar?
>>
>> Is AdoServer a complied, standalone application, or a linked library?  In either case, it might be hard to reveal what needs to be revealed.
>>
>> No response to me required... clearly.
>>
>> David A. Smith
>>

[toc] | [prev] | [next] | [standalone]


#7801

FromJames Martin <james@northwoodlumber.com>
Date2015-02-26 08:18 -0500
Message-ID<mcn661$21a$1@dont-email.me>
In reply to#7798
OK, I will try a regular databrowser. I doubt there will be a difference 
because even a fieldget() from the server gives the wrong data. I doubt 
that bBrowser is the problem.

No doubt there is something wring in the connection between 
Adoconnection and the ADO driver. I don't know how you could see the 
actual data without VO2ADO.

I am experimenting with the .net driver and C#, but the processor on one 
of my computers just quit and I need to get everything working in 
Windows 8.1.

James

On 15-02-25 05:08 PM, Karl Faller wrote:
> James,
>> Well it seems to come down to major changes:
>>
>> 1.- Use ADO and change all my numeric fields to character and convert
>> data as it goes and comes from the database.
> I know nothing about AdoServer, but i can't imagine, that it's not
> able to correctly read numerics. BTW, presume you  talk about Vo2Ado?
> If the latter, you could contact Robert, but unfortunately for you
> he's just gone on a 2 month tour on the southern hemisphere ;-(
>
> The next thing i would try is use the Server NOT with bBrowser, but
> with a regular datawindow. If you see the same, bBrowser is faultless,
> if not, you might contact Joachim...
>
> Karl
>
>> 2.- Get ODBC going. It works well on the terminal login I program in,
>> but in any other terminal I can't get ODBC to work, even if it is
>> configured the same. Does anyone have ideas as to what could keep ODBC
>>from working on other terminal logins?
>>
>> James
>>
>> On 15-02-25 09:44 AM, dlzc wrote:
>>> To the Group:
>>>
>>> On Wednesday, February 25, 2015 at 3:03:30 AM UTC-7, Malcolm G wrote:
>>>> On 24/02/2015 23:11, James Martin wrote:
>>>>> Depending on the formatting in bBrowser I get
>>>>> 199.00 or 199. But the AdoServer data is 199
>>>>
>>>> Sounds odd.
>>>>
>>>> I don't recognise the problem, but don't use
>>>> ADOServer.
>>>>
>>>> What I would do with those symptoms
>>>>
>>>> 1) look at the value of floatformat(uvalue,18,4)
>>>> in case there is something odd happening with
>>>> the display code.
>>>>
>>>> 2) Look at the table/view definition to see what
>>>> the column type is. float or numeric(10,2) etc
>>>>
>>>> 3) Say what version of VO I was testing with
>>>
>>> Does VO have the equivalent of SET DECIMALS?
>>>
>>> Does AdoServer configure itself automatically off data format, or does it require initialization via "pictures" or similar?
>>>
>>> Is AdoServer a complied, standalone application, or a linked library?  In either case, it might be hard to reveal what needs to be revealed.
>>>
>>> No response to me required... clearly.
>>>
>>> David A. Smith
>>>

[toc] | [prev] | [next] | [standalone]


Page 1 of 2  [1] 2  Next page →

Back to top | Article view | comp.lang.clipper.visual-objects


csiph-web