如何压缩拆分数据库？ [英] How to Compact a Split Database?
问题描述
当您经常添加和删除记录
时，会注意到对数据库进行膨胀的访问。我一直把我的设置紧凑，这很有效。
很棒。现在根据大家的建议，我拆分了我的数据库，所以数据在
的第二个（后端）数据库中，并且链接了所有表。但是，现在当我关闭数据库时，它会压缩前端，因为那是'开放的，
和后端增长。
我现在必须单独手动打开和关闭后端只需要
压缩它。
当然有更好的方法吗？
谢谢，
拉里L
Access is noted for bloating a database when you add and delete records
frequently. I have always had mine set to compact on close, and that works
great. Now after everyone''s advice I split my database, so the data is in
a second (back-end) database with all the tables linked. However, now when
I close the database, it compacts the front end, since that''s what''s open,
and the back-end grows.
I now have to manually open and close the back-end seperately just to
compact it.
Surely there is a better way?
Thanks,
Larry L
推荐答案
2004年1月7日星期三09:33:59 GMT， la***@somewhereinhawaii.net （Larry L）写道：
On Wed, 07 Jan 2004 09:33:59 GMT, la***@somewhereinhawaii.net (Larry L) wrote:
当您经常添加和删除记录时，会注意到对数据库进行膨胀的访问。我总是将我的设置紧凑，这很有效。现在，根据大家的建议，我拆分了数据库，因此数据位于第二个（后端）数据库中，并且所有表都已链接。然而，现在当我关闭数据库时，它压缩了前端，因为那是'开放的，
和后端的增长。
我现在必须单独手动打开和关闭后端才能压缩它。
肯定有更好的方法吗？
谢谢，
Larry L
Access is noted for bloating a database when you add and delete records
frequently. I have always had mine set to compact on close, and that works
great. Now after everyone''s advice I split my database, so the data is in
a second (back-end) database with all the tables linked. However, now when
I close the database, it compacts the front end, since that''s what''s open,
and the back-end grows.
I now have to manually open and close the back-end seperately just to
compact it.
Surely there is a better way?
Thanks,
Larry L
嗯，这不仅仅是膨胀。你需要将数据库从时间压缩到
到时间来优化表索引，并清理新生的腐败，然后它会出现症状。
是的，有一个拆分的前端数据库，你需要一种定期的方法来压缩数据库，你可以通过使用
$ b $运行Access来实现自动化。 b / compact参数。请参阅启动命令行选项;在访问帮助中获取
详细信息。
Well, it''s not just the bloating. You need to compact the database from time
to time to optimize the table indexes, and clean up nascent corruption before
it presents symptoms.
Yes, with a split front-back end database, you need a way to periodically
compact the database, and you can automate that by running Access with the
/compact parameter. See "Startup command-line options" in the Access help for
details.
" Steve Jorgensen" <无**** @ nospam.nospam> escreveu na mensagem
新闻：做******************************** @ 4ax.com ...
"Steve Jorgensen" <no****@nospam.nospam> escreveu na mensagem
news:do********************************@4ax.com...
2004年1月7日星期三09:33:59 GMT， la *** @ somewhereinhawaii.net （Larry L）
写道：
On Wed, 07 Jan 2004 09:33:59 GMT, la***@somewhereinhawaii.net (Larry L) wrote:
当您经常添加和删除记录时，会注意到对数据库进行膨胀的访问。我总是将我的设置紧凑，并且
工作很大。现在，根据大家的建议，我拆分了数据库，因此数据位于第二个（后端）数据库中，并且所有表都已链接。然而，现在
当我关闭数据库时，它压缩了前端，因为那是'b $ b打开的，后端增长。
我现在必须单独手动打开和关闭后端才能压缩它。
当然有更好的方法吗？
谢谢，
拉里
嗯，这不仅仅是腹胀。你需要不时地从
Access is noted for bloating a database when you add and delete records
frequently. I have always had mine set to compact on close, and that worksgreat. Now after everyone''s advice I split my database, so the data is in
a second (back-end) database with all the tables linked. However, now whenI close the database, it compacts the front end, since that''s what''s open,and the back-end grows.
I now have to manually open and close the back-end seperately just to
compact it.
Surely there is a better way?
Thanks,
Larry L
Well, it''s not just the bloating. You need to compact the database from
压缩数据库来优化表索引，并在出现症状之前清理新生的腐败
。
是的，使用拆分的前端数据库，您需要一种定期压缩数据库的方法，并且可以通过使用
/ compact参数运行Access来自动执行此操作。请参阅启动命令行选项;在Access中帮助
获取详细信息。
time to time to optimize the table indexes, and clean up nascent corruption
before it presents symptoms.
Yes, with a split front-back end database, you need a way to periodically
compact the database, and you can automate that by running Access with the
/compact parameter. See "Startup command-line options" in the Access help
for details.
另一个不错的CDMA从前端压缩BE的解决方案：
（通知自动换行）
http://groups.google.com/groups?hl=p...254024.9.0.131
Roberto
another nice "CDMA" solution to compact BE from te Front End:
(notice word wrap)
http://groups.google.com/groups?hl=p...254024.9.0.131
Roberto
fo ***** @ invalid .com （Roberto Spier）在
< bt ************ @ ID-66191.news.uni-berlin.de>中写道：< br>
fo*****@invalid.com (Roberto Spier) wrote in
<bt************@ID-66191.news.uni-berlin.de>:
另一个不错的CDMA从前端压缩BE的解决方案：
（通知自动换行）
http://groups.google.com/groups?hl=p...fe=off&threadm
= Xns907570C9Alylefairyahoocom％4024.9.0.131& rnum = 1& prev = / groups％3Fhl
％3Dpt％26lr％3D％26ie％3DUTF-8％26safe％3Doff％26selm％3DXns907570C9Alylefa
iryahoocom％254024.9.0.131
another nice "CDMA" solution to compact BE from te Front End:
(notice word wrap)
http://groups.google.com/groups?hl=p...fe=off&threadm
=Xns907570C9Alylefairyahoocom%4024.9.0.131&rnum=1 &prev=/groups%3Fhl
%3Dpt%26lr%3D%26ie%3DUTF-8%26safe%3Doff%26selm%3DXns907570C9Alylefa
iryahoocom%254024.9.0.131
一个非主题观察：
这些Google URL实际上只需要一个参数， selm参数。
所以，这个URL会让你看到同一篇文章：
http://groups.google.com/groups?selm...airyahoocom%40
24.9.0.131
获取此URL的最简单方法是以原始的
格式查看文章，并删除& output = gplain参数。
此外，这将以您自己的语言为您提供Google，而您的
网址是特定于语言的。
-
David W. Fenton http：// www。 bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc
An off-topic observation:
These Google URLs really only need one argument, the selm argument.
So, this URL gets you to the same article:
http://groups.google.com/groups?selm...airyahoocom%40
24.9.0.131
The simplest way to get this URL is to view the article in original
format and remove the &output=gplain argument.
Also, this will get you Google in your own language, whereas your
URL was language-specific.
--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc
这篇关于如何压缩拆分数据库？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
