Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.clipper.visual-objects > #12832
| From | Arne Ortlinghaus <Arne.Ortlinghaus@acs.it> |
|---|---|
| Newsgroups | comp.lang.clipper.visual-objects |
| Subject | Re: Issue with the Varchar(Max) datatype |
| Date | 2020-02-09 16:42 +0100 |
| Organization | Aioe.org NNTP Server |
| Message-ID | <r1p99o$lgl$1@gioia.aioe.org> (permalink) |
| References | <fa9e7d25-cdcb-40e7-b171-7b137541b606@googlegroups.com> |
Hi Stefan, perhaps you can try limiting the amount of characterers using substr(xxx, 1, 1000) from ... This way ODBC is also forced to use another type of data binding. Arne Stefan Überbacher wrote: > Hello, > > if you read the content of a Varchar (Max) column from a MS SQL Server 17 database with a VO-SQLSelect (VO 2.8 SP3), you get an empty string, regardless of the ODBC driver (SQL Server or SQL Server Native client). How can that be? I mean, Varchar (Max) is a commonly used data type. > Unfortunately MS SQL Server does not know the Long Varchar data type, because it is handled correctly by the SQLSelect. >
Back to comp.lang.clipper.visual-objects | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Issue with the Varchar(Max) datatype Stefan Überbacher <info@sanosoft.com> - 2020-02-07 05:06 -0800
Re: Issue with the Varchar(Max) datatype "Jamal" <noooospam@example.com> - 2020-02-07 23:12 -0500
Re: Issue with the Varchar(Max) datatype Stefan Überbacher <info@sanosoft.com> - 2020-02-09 22:48 -0800
Re: Issue with the Varchar(Max) datatype Arne Ortlinghaus <Arne.Ortlinghaus@acs.it> - 2020-02-09 16:42 +0100
Re: Issue with the Varchar(Max) datatype Stefan Überbacher <info@sanosoft.com> - 2020-02-09 22:47 -0800
csiph-web