[AccessD] Property Value is too large

[John Colby]

So what if we design a page on disk as 64K?

On Mon, May 15, 2023 at 12:49 PM Jim Dettman via AccessD <
accessd at databaseadvisors.com> wrote:

> << It turns out that there is a limit to the size of a table definition
> that
> Acceess can store (2KB ? )>>
>
>  Yes.  JET/ACE doesn't have split pages, so a table def must fit on a
> single
> page of 4096 bytes.  With Unicode and text taking up 2 bytes, that hovers
> around 2000 bytes in general.
>
>  "Record too large" is the corresponding error for data.
>
> Jim.
>
> -----Original Message-----
> From: AccessD On Behalf Of Stuart McLachlan
> Sent: Sunday, May 14, 2023 6:27 PM
> To: Access Developers discussion and problem solving
> <accessd at databaseadvisors.com>
> Subject: [AccessD] Property Value is too large
>
> First time I've run across this in 30 years. I've been developing contantly
> in  Access since
> 1993 and never seen it before.
>
> When trying to add another field to a table, I got the message "Property
> Value is too Large"
> and couldn''t save the change. In fact I couldn't even save the table if I
> deleted a field in it - I
> got the same error
>
> This particular , table (which I did not design - but a couple of people
> here might recognise)
> had 178 fields!   Many of the fields had "Lookup" Comboxes specified
> containing long SQL
> select statements. Also a load of long "Descriptions".
>
> It turns out that there is a limit to the size of a table definition that
> Acceess can store (2KB ? )
> and  this is not just for the table structure , it  includes the Lookup and
> Description data for
> each field and the Index definitions. ( there are 20 indexes specified for
> this table, even just
> trying to delete one and saving the table gave the same message).
>
> After I cleaned a lot of the garbage out (primarily Lookup comboxes),  I
> was
> able to add the
> field.
>
> Yet another reason why I dislike specifying anything other than the default
> for field display in
> the table design - IMNSHO, that's NOT where user interfaces should be
> specified!!!
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> https://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> https://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>


-- 
John W. Colby
Colby Consulting