Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.clipper.visual-objects > #7800
| Path | csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!news.swapon.de!eternal-september.org!feeder.eternal-september.org!mx02.eternal-september.org!.POSTED!not-for-mail |
|---|---|
| From | James Martin <james@northwoodlumber.com> |
| Newsgroups | comp.lang.clipper.visual-objects |
| Subject | Re: Precision in SQL |
| Date | Thu, 26 Feb 2015 08:11:08 -0500 |
| Organization | A noiseless patient Spider |
| Lines | 35 |
| Message-ID | <mcn5o7$vv1$1@dont-email.me> (permalink) |
| References | <mci656$2bq$1@dont-email.me> <mciofd$1dq$1@speranza.aioe.org> <mciqii$tg2$1@dont-email.me> <acspea1t0bkmvv0msbv1bmpl4oq9e2d0uc@4ax.com> <mcj054$nm6$1@dont-email.me> <R5hHw.131581$C91.89107@fx22.am4> <6c2bab78-268c-4ff9-acd7-848ba040b966@googlegroups.com> <mckv9u$7hv$1@dont-email.me> <2LBHw.869553$fp4.122640@fx10.am4> |
| Mime-Version | 1.0 |
| Content-Type | text/plain; charset=windows-1252; format=flowed |
| Content-Transfer-Encoding | 7bit |
| Injection-Date | Thu, 26 Feb 2015 13:06:15 +0000 (UTC) |
| Injection-Info | mx02.eternal-september.org; posting-host="6dabfc096e408b3ae1004704b7637f83"; logging-data="32737"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19krNhSgJLi+XBJ20a+CZox" |
| User-Agent | Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 |
| In-Reply-To | <2LBHw.869553$fp4.122640@fx10.am4> |
| Cancel-Lock | sha1:gF6qHhg3NfsCYiJcWSqCVxOqM38= |
| Xref | csiph.com comp.lang.clipper.visual-objects:7800 |
Show key headers only | View raw
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. >
Back to comp.lang.clipper.visual-objects | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
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
csiph-web