记录太大MS Access运行时错误 [英] Record is too large MS Access runtime error

查看:144
本文介绍了记录太大MS Access运行时错误的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

在MS Access中,我的一个应用程序的表异常大.它猛烈地破坏了一些规范化规则,但对于这种小型应用程序来说还是可以的.它具有约100个字段(列).我已经阅读了此处的限制规范 但看不到我在哪里违反了这些规定.大多数字段是文本字段,范围从几个单词到几个句子.我的问题是:

I have an abnormally large table for one of my applications in MS Access. It violently breaks some rules of normalization, but is otherwise fine for this small application. It has ~100 fields(columns). I have read the limitation specifications here but can't see where I violate any of these. Most of the fields are text fields, and range from a couple words to a couple of sentences. My questions are:

  1. 是否有一种方法可以得到比记录太大"更具描述性的错误,以便我可以确定如何使其更小?

  1. Is there a way to get a more descriptive error than "record is too large", so that I can determine how to make it smaller?

将文本"字段更改为备注"字段会减小记录的大小吗?

Would changing my 'text' fields to 'memo' fields decrease the size of my record?

乍看之下,所有可能违反的规范中,:当字段的UnicodeCompression属性设置为是:: 4,000"时,记录中的字符数(备注"和"OLE对象"字段除外)强>
似乎是最有可能的罪魁祸首.

At first glance, of all of the specifications potentially violated, this :Number of characters in a record (excluding Memo and OLE Object fields) when the UnicodeCompression property of the fields is set to Yes :: 4,000
appears to be the most likely culprit.

  1. 这种违反可能会给记录太大"运行时错误(同时填写表格).

  1. Would this violation potentially give the "record is too large" runtime error(while filling out a form).

将UnicodeCompression属性设置为否"会对性能产生正面或负面影响吗?

Would setting the UnicodeCompression property to 'no' positively or negatively impact the performance?

推荐答案

备注字段可能是答案.记录限制规则不包括备忘录数据类型.

Memo fields are likely to be the answer. The record limitation rules do not include memo data type.

这篇关于记录太大MS Access运行时错误的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆