memo Field
Richard Kreiss
rkreiss at verizon.net
Wed Nov 10 07:39:36 PST 2010
> -----Original Message-----
> From: filepro-list-bounces+rkreiss=verizon.net at lists.celestial.com
> [mailto:filepro-list-bounces+rkreiss=verizon.net at lists.celestial.com] On
> Behalf Of Kenneth Brody
> Sent: Tuesday, November 09, 2010 7:47 PM
> To: Dennis DIller
> Cc: filepro-list at lists.celestial.com
> Subject: Re: memo Field
>
> On 11/9/2010 5:47 PM, Dennis DIller wrote:
> [...]
> > I have two questions can someone answer them for me.
> >
> > This file has 1310859 records by adding this field to the file what
> > will it do for disk space does every record get memo field a how much
> space will it take up?
>
> If the memo is a new field (ie: it's not used in any of those records),
then the
> memo file will be 48K in size. If you are filling a value into all
> 1,310,859 records, then a lot of it depends on just how much you are
putting
> into those memo fields.
>
> > also while browsing into this file can I use a @BK="M" to display the
> > memo field for that record. Just to have it popup and display the memo
> > details of this record user cannot edit just view?
>
> I assume you mean a browse lookup into that file? In that case, you can
> display the contents of the lookup, including a memo field, in processing.
> And you could trigger it with @BK="M" after the browse lookup.
>
Ken,
Are you indicating here that to do this a dummy field such as mm(16,memo)
should be used to hold the memo field from the file being browsed?
I would then assume (bad word) that all of the memo functions would be
available if wanted.
Richard
More information about the Filepro-list
mailing list