Tore,
It doesn't matter much in this case. Storing such redundant data in a memo field is already bloated from the start:)
Cetin

>My point is that you should only have ONE replace command, not a lot like in your sample. In a multiuser envirionment VFP will allocate a new memory block for each replace, if you do it your way, causing memo bloat.

>mPocReciept="20-09-2004 Cashier: Bob" +CHR(13)+CHR(10)
>mPocReceipt=mPocReceipt + "Pizza..........1x 8.00 =  8.00" +CHR(13)+CHR(10)
>mPocReceipt=mPocReceipt + "Topping....1x 1.00 =  1.00" +CHR(13)+CHR(10)
>Replace PocReceipt with mPocReceicpt

>
>>>>
>>This is one of many ways to get his POC data into a memo field. Bloat, well that has to be watched, but he seemed to want all the Point of Sale information in the memo field. You will have to deal with bloat.
>>
>>>Are you giving crash courses in how to create memo bloat? :-)
>>>
>>>Try to minimize the number of replaces in a memo field!
>>>
>>>>If the memo field is called lets say PocReceipt, then you could say:
>>>>
>>>>REPLACE PocReceipt WITH PocReceipt + "20-09-2004 Cashier: Bob
>>>>" +CHR(13)+CHR(10)
>>>>REPLACE PocReceipt WITH PocReceipt + "Pizza..........1x 8.00 = 8.00" +CHR(13)+CHR(10)
>>>>REPLACE PocReceipt WITH PocReceipt + "Topping....1x 1.00 = 1.00" +CHR(13)+CHR(10)
>>>>
>>>>
>>>>etc...