A Microsoft Office (Excel, Word) forum. OfficeFrustration

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » OfficeFrustration forum » Microsoft Access » Database Design
Site Map Home Register Authors List Search Today's Posts Mark Forums Read  

"Record is too large" error on only 294 fields all set to Memo?



 
 
Thread Tools Display Modes
  #11  
Old August 10th, 2007, 03:02 AM posted to microsoft.public.access.tablesdbdesign
David W. Fenton
external usenet poster
 
Posts: 3,373
Default "Record is too large" error on only 294 fields all set to Memo

John Nurick wrote in
:

Help is forgetting people who don't use the roman alphabet. I
guess it should read something like this:

Number of characters in a record (excluding Memo and OLE
Object fields) when the UnicodeCompression property of the
fields is set to Yes *and* all characters are in the Windows
(Western) character set: 4,000


Anyone who is worrying about those limits has a badly-designed
schema.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/
  #12  
Old August 11th, 2007, 03:39 AM posted to microsoft.public.access.tablesdbdesign
external usenet poster
 
Posts: n/a
Default "Record is too large" error on only 294 fields all set to Memo

Anyone who is worrying about those limits has a badly-designed
schema.


Well I guess, although I think some people actually use their database
to contain data, not just pointers to data, nor data about data.

The problem I have is that some of the databases I manage contain
simple multi-dimensional data. I can see that if I had complex
multi-dimensional data, I would want to switch to a non-relational
model, but for simple two-dimensional data, it's easier just to put
the audit or regulatory dimension inline.

Since there is, by definition, no updates or deletions to audit
data, there are no update or delete anomalies. Since there
has always been less than 0.5GB data, there have never been
any data size issues.

You can just replace all of your tables with super-index tables,
but that makes the primary dimension significantly more difficult,
and you loose the basic advantage of a relational database.


(david)


"David W. Fenton" wrote in message
. 1...
John Nurick wrote in
:

Help is forgetting people who don't use the roman alphabet. I
guess it should read something like this:

Number of characters in a record (excluding Memo and OLE
Object fields) when the UnicodeCompression property of the
fields is set to Yes *and* all characters are in the Windows
(Western) character set: 4,000


Anyone who is worrying about those limits has a badly-designed
schema.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/



 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Forum Jump


All times are GMT +1. The time now is 06:51 AM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 OfficeFrustration.
The comments are property of their posters.