Re: ActualSize returns -1 for Text fields
- From: "Rod da Silva" <RodDaSilva@xxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 26 Sep 2005 06:39:16 -0400
Mark
> If you know that max size of the field's content will stay under 8060 -
> [size of other fields] and/or truncation is tolerable, and you only need
> read-only access to it, you can convert it to varchar in the SQL
statement:
>
> SELECT CONVERT(varchar(6000), [MyTextCol1]) As MyTextCol1 FROM ...
Thanks for the suggestion but unfortunatly neither of those criteria holds
for my situation. My table has multiple Text fields, anyone of which is
typically larger than the 8060 limit (which is the reason I am using Text
CLOB fields in the first place) and I need read/write access to them as
well.
What I need here is a fix from MS.
Rod
.
- References:
- ActualSize returns -1 for Text fields
- From: Rod da Silva
- Re: ActualSize returns -1 for Text fields
- From: Mark J. McGinty
- Re: ActualSize returns -1 for Text fields
- From: Rod da Silva
- Re: ActualSize returns -1 for Text fields
- From: Mark J. McGinty
- ActualSize returns -1 for Text fields
- Prev by Date: Re: ActualSize returns -1 for Text fields
- Next by Date: How to turn a string into an ADO.Stream?
- Previous by thread: Re: ActualSize returns -1 for Text fields
- Next by thread: Re: ActualSize returns -1 for Text fields
- Index(es):