Hello Bill, Friday, November 8, 2002, 2:47:53 PM, you wrote:
Many thanks for your helpful response. BT> When I need long text fields in MapInfo, I create a second that BT> looks like: BT> [Table: Memo] BT> Memo_id int BT> Sequence smallint BT> Text char(64) BT> And in the main table I store the memo_id where I want to BT> reference a memo field. So far so good. BT> Then I have written memo support functions in MapInfo like BT> MemoRead(), MemoWrite(), MemoDelete(), MemoEdit() and BT> MemoSearch(). You can pass long text strings between your app and BT> these functions, but they have to do the job of manipulating the BT> long strings to fit the "memo" table. In other word, handle a long BT> text strings as a series of short text strings ordered by BT> sequence. Write these functions as a library module, and link to BT> any app where you need to support memo fields, and you'll find BT> it's quite easy to support long strings. Here you lose me a bit, as I am not a developer. BT> However, you can't use Access memo fields with MapInfo because BT> MapInfo will just treat them like char(254) data types. BT> You need to use a different data structure and write supporting BT> functions. I am not wed to Access, if there are other ways to do it. Are your supporting functions working with native MapInfo tables? BT> Even then with MapInfo's textedit boxes you are limited BT> to strings no larger than 32K and containing no more than 49 BT> newlines. I have trouble imagining how this actually works. However the 32K 49 newline limit could be okay, it certainly beats 254 characters. Where can I get the long string support functions ... I don't think that I will be writing them myself, not in this lifetime, anyway. -- Best regards, David --------------------------------------------------------------------- List hosting provided by Directions Magazine | www.directionsmag.com | To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Message number: 4002
