Hi, Ron.
Lyle's suggestion is currently in "Message 7" of this thread of messages:
http://groups.google.com/groups?hl=e...3c87845a1612c1
HTH.
Gunny
See
http://www.QBuilt.com for all your database needs.
See
http://www.Access.QBuilt.com for Microsoft Access tips.
(Please remove ZERO_SPAM from my reply E-mail address, so that a message
will be forwarded to me.)
"Ron" <ronSPAMBLOCKERwest777@earthlink.com> wrote in message
news:oEY2d.1037$qA6.577@newsread3.news.pas.earthli nk.net...[color=blue]
> And where might "Lyle Fairfield's suggestion to first save the text as
> files..." be found?
>
> TIA
> ron
>
> "'69 Camaro" <ForwardZERO_SPAM.To.69Camaro@Spameater.orgZERO_SP AM> wrote[/color]
in[color=blue]
> message news:yDI2d.442$je.99@trnddc04...[color=green]
> > Hi, Lauren.
> >
> > The limits are due to constraints of the Jet architecture. Since Access
> > 2003 also uses Jet 4.0, these constraints have not changed since the[/color]
> Access[color=green]
> > 2K version. The maximum limits for a memo field are still 65,535[/color]
> characters[color=green]
> > entered into a text box and 1 GB when the characters are entered into[/color][/color]
the[color=blue][color=green]
> > field programmatically.
> >
> > And the prevalence of database corruption due to bound memo fields is[/color][/color]
just[color=blue][color=green]
> > as great in Access 2003 as it was in Access 2K. I strongly suggest that[/color]
> you[color=green]
> > unbind the memo field on your bound form. You'll get two benefits:[/color][/color]
less[color=blue][color=green]
> > likelihood of corruption and the ability to paste up to 1 GB of text[/color][/color]
into[color=blue][color=green]
> > the text box on a form.
> >
> > And if you take Lyle Fairfield's suggestion to first save the text as[/color]
> files,[color=green]
> > then use ADO and indexing services to connect to them, you'll receive[/color]
> other[color=green]
> > benefits as well, including a much smaller database.
> >
> > HTH.
> >
> > Gunny
> >
> > See
http://www.QBuilt.com for all your database needs.
> > See
http://www.Access.QBuilt.com for Microsoft Access tips.
> >
> > (Please remove ZERO_SPAM from my reply E-mail address, so that a message
> > will be forwarded to me.)
> >
> >
> > "Lauren Wilson" <???@???.???> wrote in message
> > news:shfmk0h15hfv49fouc31n7tlb84spn27hc@4ax.com...[color=darkred]
> > > Hi folks,
> > >
> > > In light of the info below, does anyone know if the limits on editable
> > > characters in a memo field bound to a text box has been improved in
> > > Access 2003?
> > >
> > >
> > >
> > > On Thu, 12 Aug 2004 09:44:13 GMT, "'69 Camaro"
> > > <Black_hole.To.69Camaro@Spameater.org> wrote:
> > >
> > > >Hi, Lauren.
> > > >
> > > >You are trying to paste too much into the text box. Access 2K has[/color][/color][/color]
two[color=blue][color=green][color=darkred]
> > > >limits on Memo field size:
> > > >
> > > >1.) Maximum number of characters when data is entered through the[/color][/color][/color]
user[color=blue][color=green][color=darkred]
> > > >interface: 65,535.
> > > >2.) Maximum number of characters when data is entered[/color][/color]
> programmatically:[color=green]
> > 1[color=darkred]
> > > >GB.
> > > >
> > > >You can find these limits, as well as others, by entering the word
> > > >specifications in Access 2K help.
> > > >
> > > >Also, a known cause of Access database corruption is Memo fields[/color][/color][/color]
being[color=blue][color=green][color=darkred]
> > > >edited through bound text boxes. Using VBA code to input the 200K
> > > >characters from the text box into the record will accommodate your[/color][/color]
> needs[color=green][color=darkred]
> > > >and, hopefully, prevent database corruption.
> > > >
> > > >HTH.
> > > >
> > > >Gunny
> > > >
> > > >See
http://www.QBuilt.com for all your database needs.
> > > >See
http://www.Access.QBuilt.com for Microsoft Access tips.
> > > >
> > > >
> > > >"VRWC" <???@???.zip> wrote in message
> > > >news:jfilh0dl1fret389klgb8k5i1mf5bckel4@4ax.com.. .
> > > >>
> > > >> That should be plenty. I thought maybe running out of string space
> > > >> was causing the error I'm getting from pasting about 200K[/color][/color][/color]
characters[color=blue][color=green][color=darkred]
> > > >> into a text box bound to a memo field. When I arrive on such[/color][/color][/color]
records[color=blue][color=green][color=darkred]
> > > >> and place the cursor into the text box, I get a message that says
> > > >> "text too large to be edited".
> > > >>
> > > >> Any clues?
> > > >>
> > > >>
> > > >> On Tue, 10 Aug 2004 20:59:55 -0700, Tom van Stiphout
> > > >> <no.spam.tom7744@cox.net> wrote:
> > > >>
> > > >> >On Tue, 10 Aug 2004 22:35:29 -0500, Lauren Wilson <???@???.com>[/color][/color]
> wrote:[color=green][color=darkred]
> > > >> >
> > > >> >Very large, but in my testing strangely unpredictable. I expected[/color][/color]
> 2^32[color=green][color=darkred]
> > > >> >- 1, but that was not the case.
> > > >> >
> > > >> >Here is the test code I ran:
> > > >> >Sub Test()
> > > >> >Dim s As String
> > > >> >Const EXPONENT As Integer = 28
> > > >> >s = String$(2 ^ EXPONENT - 1, 65)
> > > >> >Debug.Print EXPONENT, Len(s)
> > > >> >End Sub
> > > >> >
> > > >> >For values of EXPONENT greater than 28 I received an Out Of String
> > > >> >Space error. Still, at least 268 million characters - hopefully[/color][/color]
> that's[color=green][color=darkred]
> > > >> >enough?
> > > >> >
> > > >> >-Tom.
> > > >> >
> > > >> >
> > > >> >>Access 2K
> > > >> >>
> > > >> >>dim MyStr as string
> > > >> >>
> > > >> >>What is the maximum amount of text or bytes that this variable[/color][/color][/color]
can[color=blue][color=green][color=darkred]
> > > >> >>store? Does anyone know?
> > > >>
> > > >
> > >[/color]
> >
> >[/color]
>
>[/color]