String Gets Truncated when reading it back

[jalil.feghhi]

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

 

[John W. Vinson/MVP]

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

If the Query upon which the recordset is based attempts to sort by
StoreID, the field will be truncated to 255 bytes. Just don't specify
a sort, or else use a calculated field Left([storeID], 255) for
sorting.

 

[a a r o n _ k e m p f]

wow.. good stuff.

Or, move to SQL Server and use ADP if you don't want crappy limits on
your sorting

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?

-Jalil

If the Query upon which the recordset is based attempts to sort by
StoreID, the field will be truncated to 255 bytes. Just don't specify
a sort, or else use a calculated field Left([storeID], 255) for
sorting.