Text Box or String > 32K -- Problem?

  • Thread starter Thread starter Rusty in Illinois
  • Start date Start date
R

Rusty in Illinois

Hi all -

Working in Access 97, I have a table with a memo field that can exceed
32K. Apparently this is a problem for the Text Box controls on the form
for the table. I get a message "Text too long to be edited" and the
field goes blank.

What is the proper way to display (or edit though I don't need to edit
in this situation) a memo field that can contain more than 32K of data?
I also have a similar problem parsing the text in VBA as it appears I'm
not getting data beyond the 32K point in the text.

All this is encountered while processing MODULE objects in a system
self-documentation application.

Unfortunately I'm stuck in A97 for now, though I'm interested in
comments about later versions as well.

(In a breach of nntp etiquette, this note was also posted independently
in m..p..a..forms. I hope that doesn't prevent helpful responses.)

Thanks...
 
Rusty said:
Working in Access 97, I have a table with a memo field that can exceed
32K. Apparently this is a problem for the Text Box controls on the form
for the table. I get a message "Text too long to be edited" and the
field goes blank.

What is the proper way to display (or edit though I don't need to edit
in this situation) a memo field that can contain more than 32K of data?
I also have a similar problem parsing the text in VBA as it appears I'm
not getting data beyond the 32K point in the text.

All this is encountered while processing MODULE objects in a system
self-documentation application.

Unfortunately I'm stuck in A97 for now, though I'm interested in
comments about later versions as well.
Click to expand...

Either you are counting incorrectly or there is something
else going on. An A97 text box can hold up to 64K
characters. If you only manipulate it in code, string
variables and Memo fields can hold over 1GB of data (but an
MDB file is limited to 1GB).
 
Marshall ...

Thanks for the response.

I vote for "something else going on". I've traced the code and checked
lengths on various fields and objects while debugging the code. I've
changed my inserts on the database to a loop of AppendChunks and it
still seems like I'm not getting the proper data. I say that because a
Len([MemoFieldName]) in a query and still get 32768 as the largest (and
frequent) value. While debugging I saw a module whose Len was over
120,000 characters.

I also parse the ModuleObject.Module using a Module.Lines method to get
individual routines out of the module. It seems as though this didn't
make it past the 32K line because I am missing routines in my output
tables.

Could this be an incorrect VBA library, or some other old version of
Access97? I'm running VBA332.DLL, MSACC8.OLB, and DAO2535.tlb according
to my References in VBA.

I'm scratching my head, or I need a link to a reference on handling
CLOBs > 32K (and Module objects) in Access.

Thanks...
 
Rusty said:
I vote for "something else going on". I've traced the code and checked
lengths on various fields and objects while debugging the code. I've
changed my inserts on the database to a loop of AppendChunks and it
still seems like I'm not getting the proper data. I say that because a
Len([MemoFieldName]) in a query and still get 32768 as the largest (and
frequent) value. While debugging I saw a module whose Len was over
120,000 characters.
Click to expand...

120K characters will never fit into a text box.

I also parse the ModuleObject.Module using a Module.Lines method to get
individual routines out of the module. It seems as though this didn't
make it past the 32K line because I am missing routines in my output
tables.
Click to expand...

What is application doing??? Some kind of source code
management control?

Could this be an incorrect VBA library, or some other old version of
Access97? I'm running VBA332.DLL, MSACC8.OLB, and DAO2535.tlb according
to my References in VBA.
Click to expand...

I'm not very good at keeping track of all these library
names and versions, but I think DAO2535 is something that
bridges an old A2 back end data mdb to an A97 front end.
This may very well be the problem, try using DAO351 (with
all service packs applied).
 
Back
Top