压缩/压缩OnClose [英] Compact / Compress OnClose

查看:81
本文介绍了压缩/压缩OnClose的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

Access有一个Compact on Close选项。非常好,因为每次访问任何.mdb文件时都应该停止大小的增加。


我的问题是,这样安全吗?以前我会在尝试压缩之前制作备份副本。所以现在我可以自动完成,无需备份副本,也无需向用户介绍此过程,以及这一切意味着什么。


我使用Outlook Express,它达到了2GB,并失败了。我发现我应该偶尔做一次压缩。我没有意识到这一点,我确信大多数用户都不知道这是一个数据库程序,需要进行压缩。


所以如果微软不这样做的话对于Outlook Express的自动紧凑型,我可以信任Compact for Close for Access吗?


OldBirdman

Access has an option for Compact on Close. Very good, as that should stop a major increase in size every time any .mdb file is used by Access.

My question is, Is this safe? It used to be that I would make a backup copy before I tried to compress. So now I can do it automatically, without a backup copy and without having to teach users about this procedure, and what it all means.

I use Outlook Express, and it reached 2GB, and failed. I find I was supposed to be doing a compress occasionally. I didn''t realize this, and I''m sure most users are not aware that this is a database program, and needs to be compacted.

So if Microsoft does not do an automatic compact for Outlook Express, can I trust the Compact at Close for Access?

OldBirdman

推荐答案

请停止使用术语压缩并坚持使用 h compact 压缩既令人困惑又不准确!


使用 Compact on Close 选项经常被认为是Access中的损坏原因数据库。我经常看到这些报告,我从不使用该选项,并且在压缩之前始终备份。您的选择!


现在,关于Outlook Express。原因是大多数用户不知道这是一个数据库程序很简单; 它不是数据库程序,它是一个电子邮件程序!


是的,建议您不时压缩文件。与基于Web的电子邮件程序不同,您的邮件存储在电子邮件服务器上,OE邮件存储在您的硬盘上。建议使用压缩以节省PC上的存储空间,而不是因为Access存在2 GB的限制。它被破坏的原因有很多。用户引发的最大原因之一是一旦启动就会中断紧凑的过程!具有讽刺意味的是,另一个是电子邮件扫描反病毒程序。


这里有两个很好的链接,可以解释Outlook Express压缩的细节,以及全面概述腐败/不良性能的所有原因。
http://email.about.com/od/ outlookexp ... compact_oe.htm

http://www.microsoft.com/windows/ie/...ption.mspx#EEB


Linq ; 0)>
Please stop using term compress and stick with compact! Compress is both confusing and inaccurate!

Using the Compact on Close option has often been cited as a cause of corruption in Access databases. I''ve seen these reports often enough that I never use the option and always backup before compacting. Your choice!

Now, about Outlook Express. The reason "most users are not aware that this is a database program" is very simple; it''s not a database program, it''s an email program!

Yes, it''s recommended that you compact the files from time to time. Unlike web-based email programs, where your messages are stored on the email servers, with OE the messages are stored on your hard drive. Compacting is recommended in order to save storage space on your PC, not because there is a 2 GB limit as is true with Access. There are a number of reasons why it becomes corrupted. One of the biggest, user induced causes is interrupting the compact process once it has started! Another is, ironically, email scanning anti-virus programs.

Here are two excellent links that explain the ins and outs of Outlook Express compacting as well as a comprehensive overview all the causes of corruption/poor performence in it.

http://email.about.com/od/outlookexp...compact_oe.htm

http://www.microsoft.com/windows/ie/...ption.mspx#EEB

Linq ;0)>


正如Linq所说 - 我会谨慎使用CompactOnClose选项。我总是使用Compact选项而不打开数据库。这样它就会要求源和目标数据库名称(当然是内置备份)。

我也可以从我的数据库中的命令按钮获取标准名称。
As Linq says - I''d be wary of using the CompactOnClose option. I always use the Compact option without a database open. This way it asks for source and destination database names (inbuilt backup of course).
I also get mine to work from a command button in my database for the standard ones.
展开 | 选择 | Wrap | 行号



正如Linq所说 - 我会谨慎使用CompactOnClose选项。我总是使用Compact选项而不打开数据库。这样它就会要求源和目标数据库名称(当然是内置备份)。

我也可以从我的数据库中的命令按钮获取标准名称。
As Linq says - I''d be wary of using the CompactOnClose option. I always use the Compact option without a database open. This way it asks for source and destination database names (inbuilt backup of course).
I also get mine to work from a command button in my database for the standard ones.
展开 | 选择 | Wrap | 行号


这篇关于压缩/压缩OnClose的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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