[AccessD] Memo field corruption
jimdettman at verizon.net
Thu Jan 31 14:56:53 CST 2019
Actually it puts it on a LVP (Long Value Page) only if it's > 30 bytes.
And that might be 34 or 36....it's been awhile<g>. It's a small number
none the less and I'm not sure why that number. The pointer is 16 bytes.
But if it's less than that, then the data stays with all the rest of the
From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of
Sent: Thursday, January 31, 2019 3:44 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Memo field corruption
That's a misunderstanding of the way a memo is stored compared to other
types of data.
Access uses "data pages" within the datafile to store the data. A memo
field only stores a
pointer in the record's primary data page which points to a separate data
page (or pages)
holding the actual memo data.
On 31 Jan 2019 at 9:28, Bill Benson wrote:
> RE: >>> memo content is not actually stored in the table. Only a
> pointer to its location on disk is
> I don't see how that is this possible. Locations on disk change all
> the time. Databases get copied from one location, partition, and from
> PC to network or to other PCs all the time, without memo fields losing
> their contents.
> AccessD mailing list
> AccessD at databaseadvisors.com
> Website: http://www.databaseadvisors.com
AccessD mailing list
AccessD at databaseadvisors.com
More information about the AccessD