Rafael Copquin wrote on 2014-08-11:
I'm having a Monday morning memory lapse.
I have this memo field with text inside.
I need to add a time stamp and additional text and I do it thus:
With thisform.edit1
.enabled = .t.
replace curList.pv_mo with Replicate('*',100)
Thank you Tracy
Works like a charm!
Rafael
El 11/08/2014 12:33, Tracy Pearson escribió:
Rafael Copquin wrote on 2014-08-11:
I'm having a Monday morning memory lapse.
I have this memo field with text inside.
I need to add a time stamp and additional text and I do it thus:
With
I honestly never noticed the ADDITIVE clause in the REPLACE command.
Wow...learned something new today!
From VFP Help for those who hadn't noticed this either:
ADDITIVE
Appends to the end of the memo fields replacements to memo fields.
ADDITIVE applies to replacements in memo fields only. If
Hi Rafael:
You may want to avoid memo bloat:
replace curList.pv_mo with '';
+ Replicate('*',100) + Chr(13);
+ Ttoc(Datetime()) + Chr(13);
+ Replicate('*',100) + Chr(13);
+ '' additive
each REPLACE increases the .fpt size
Thierry Nivelet
FoxInCloud
Give your VFP app a second
Hi Thierry,
I thought the same thing at first until I read that ADDITIVE clause.
Still applies to bloat concern??
Thanks,
--Michael
On 2014-08-11 11:50, Thierry Nivelet wrote:
Hi Rafael:
You may want to avoid memo bloat:
replace curList.pv_mo with '';
+ Replicate('*',100) + Chr(13);
replace. If they don't add, or cancel, then
just leave everything as is.
Dan Covill
Date: Mon, 11 Aug 2014 11:59:50 -0400
From: mbsoftwaresoluti...@mbsoftwaresolutions.com
To: profoxt...@leafe.com
Subject: Re: bottom of memo field
Hi Thierry,
I thought the same thing at first until I read
I thought the same thing at first until I read that ADDITIVE clause. Still
applies to bloat concern??
Yes !
In fact, VFP doesn't manage 'not sequential segments' (or blocs). All the memo
content must be contiguous in the .fpt file. So when size increase, VFP must
'disable' the actual blocs
Yes, it does.
Try this and watch for yourself:
CREATE TABLE t_memo (memo m)
APPEND BLANK
REPLACE memo WITH REPLICATE('0',1024*1024) additive
* look at the FPT, should have 1 MB (earlier: 0 MB, now: 1 MB)
REPLACE memo WITH REPLICATE('0',1024*1024) additive
* look at the FPT, should have 3 MB
2014-08-11 18:12 GMT+02:00 Fernando D. Bozzo fdbo...@gmail.com:
* look at the FPT, should have 3 MB (earlier: 10 MB, now: 15 MB)
You really have made 4 replaces ADDITIVE, 1 MB each one, but you have a 15
MB memo... Bloat!
This part should sey 5 replaces additive
If you PACK, then the
...or PACK MEMO :D
2014-08-11 18:16 GMT+02:00 Fernando D. Bozzo fdbo...@gmail.com:
2014-08-11 18:12 GMT+02:00 Fernando D. Bozzo fdbo...@gmail.com:
* look at the FPT, should have 3 MB (earlier: 10 MB, now: 15 MB)
You really have made 4 replaces ADDITIVE, 1 MB each one, but you have a
On 2014-08-11 12:09, Dan Covill wrote:
It may be additive, but it's still a 'replace' statement and will
create a new field in the .fpt.
My recommendation would be to extract the existing memo content into a
string memvar, then show the user that with the date/time stamp. If
they choose to add
On 2014-08-11 12:10, Jean MAURICE wrote:
In fact, VFP doesn't manage 'not sequential segments' (or blocs). All
the memo content must be contiguous in the .fpt file. So when size
increase, VFP must 'disable' the actual blocs and create new ones with
the right size.
I don't think either that VFP
At 08:59 2014-08-11, mbsoftwaresoluti...@mbsoftwaresolutions.com wrote:
Hi Thierry, I thought the same thing at first until I read that
ADDITIVE clause. Still applies to bloat concern??
I just tested it, and the answer is yes.
replace memocolumn with stufftoadd additive
is
Hi Thierry
I will follow your advice to avoid memo bloat.
Rafael Copquin
El 11/08/2014 14:03, Gene Wirchenko escribió:
At 08:59 2014-08-11, mbsoftwaresoluti...@mbsoftwaresolutions.com wrote:
Hi Thierry, I thought the same thing at first until I read that
ADDITIVE clause. Still applies to
14 matches
Mail list logo
