[AccessD] Memo Fields - Cursor positioning at the endofthememowhen the len > max integer value

Gustav Brock gustav at cactus.dk
Sun Dec 28 03:35:41 CST 2003


Hi David

Oh no - as a rule of thumb, if WordPad can hold it, your RTF box can
as well.
But storing and indeed editing of a large text is slow, so speed of
editing may set a practical limit.

/gustav


> Hey thanks Gustav, Kewl idea, not contiguous form, will try this, I presume
> the 64K limit will still apply?

>> I had the Microsoft Rich Textbox Control 6.0 (SP4) in mind.
>>
>> OLE Class: RICHTEXT.RichtextCtrl.1
>>
>>
>> > Gustav, how would you use  an RTF box -- are you suggesting a non-native
>> > control, such as one of the MS Forms controls, something else, or is
>> > there somewhere to turn a memo control into rtf?
>>
>> >> If your memo field is used on a form displaying single records only
>> >> (not contiguous records), you may be able to use an RTF (Rich Text
>> >> Format) box. Here SelStart and SelLength are Long.
>> >>
>> >> Applying this will, of course, turn your memo contents into RTF
>> >> documents which may cause an avalanche of new problems ...
>> >> On the other hand, an RTF box supports both drag and drop which may be
>> >> advantageous if your users operate with memo field contents in the 32+
>> >> K area.
>> >>
>> >> /gustav
>> >>
>> >>
>> >> >> > I use selstart to identify the end of a memo and set the
>> >> >> > cursor there, (so user can launch straight into appending
>> >> >> > text directly into the memo) however whenever the memo's
>> >> >> > length is greater than the max integer value of 32K this
>> >> >> > fails as it only works for integer values.  How can one
>> >> >> > position the cursor in a memo field that has number of
>> >> >> > characters bet the 32 and 64K len? ..



More information about the AccessD mailing list