Re: Truncation Issue w/ Strings
- From: "Dave O." <nobody@xxxxxxxxxxx>
- Date: Fri, 18 Jul 2008 14:26:03 +0100
Could you be a little less ambiguous than "big" & "very long", for some
people a "big" string will be a few hundred characters for others it's not
"very long" if its under a megabyte.
Also is "stMsg" as typo for "rstMsg"? or are you talking about different
things here.
This is an admittedly trivial example of why you should ALWAYS copy and
paste from your code rather than re-typing it into the message.
Regards - Dave O.
<jalil.feghhi@xxxxxxxxx> wrote in message
news:c5c2b21f-ec48-415d-b096-484b76ca54be@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I have an access database that has a field (type memo) that keeps very
long strings. When the value of this field is very long, my Visual
Basic 6.0 code does not return the whole value and truncates it. I
just read it using standard code like this:
storeId = rstMsg!storeId
where is defined as: Dim stMsg As ADOdb.Recordset
Everything works fine if storeid is not very big.
Does anybody know why this happens?
Thanks,
-Jalil
.
- Follow-Ups:
- Re: Truncation Issue w/ Strings
- From: jalil . feghhi
- Re: Truncation Issue w/ Strings
- References:
- Truncation Issue w/ Strings
- From: jalil . feghhi
- Truncation Issue w/ Strings
- Prev by Date: Getting problem in paper size
- Next by Date: Using Checkbox with DataRepeater
- Previous by thread: Re: Truncation Issue w/ Strings
- Next by thread: Re: Truncation Issue w/ Strings
- Index(es):
Relevant Pages
|