>>>>Anyone know a good way to pass memos longer than 255? Sybase has a varchar type which has a max of 255. The Sybase people will store them as multiple varchar records plus ID. They think I should split my memos up for them into vfp char strings plus ID. I think they should open the memo as a text and parse it themselves, but they say they can't do it. There are quite a few memos in different tables, otherwise we wouldn't be debating this. Anyone have experience with this ?
>>>
>>>I assume it's pre-System 10, otherwise I believe they have a text field type that would handle it.
>>>
>>I'll check -- frankly, all the PB/Sybase people here are quite new to their software...I'll get back when I find out...
>>
>If it is System 10 or above, then the text field type will map quite nicely. It's got a maximum length of 2 ^ 31 - 1. I think that will qualify. ;-).
>
The version is 10.0.3, which has Text type: but sybase team says:
--snip--
W.r.t using Text datatype we found following Problem :
"To write text datatype the command is Writetext ,which is a non logged state , a System Administrator must use sp_dboption to set select into/bulkcopy pn. This permits the insertion of non-logged data. After using WriteText , it is necessary to dump database. A transaction dump which is done after unlogged changes to the database is not usable in a Load transaction operation. "

Now if use the datatype "TEXT" in our database then there is a possibility to lose the text data as the transaction log does not contain text data in it . (as after each writetext we have to use "DUMP DATABASE" . That’s the reason, We changed all our datatype of text to VarChar(255) and split the records.
--snip--
I feel like I may be in the wrong forum now for this, but any ideas on either the vfp side or sybase side of things?