Access 2000需要每天修复 [英] Access 2000 needs to be repaired EVERY day
问题描述
问候！
我希望有人可以解决我遇到的问题。我有13个用户
在Access 2000上运行各种PC上的FE和新HP服务器上的BE
与Windows 2003，充足的电量和RAM。问题是，我开始得到
一个错误，我的数据库是一个无法识别的格式。这已经发生了大约3次，第一次让我失去了大约3周的票价
（DB正在运行一个交付票系统）。现在我收到一个错误
数据库需要修复。我必须让每个人都出去，所以
远远不能紧凑和修理没有问题。
有没有人在那里想到为什么这个正在发生如何
阻止它？我担心我会被数据抽屉抓住
下来.....
提前感谢您提供的任何帮助...... ..
Greeting!
I hope someone can shine a light on a problem I am having. I have 13 users
on Access 2000 running FE from various PC and the BE on a new HP Server
with Windows 2003, plenty of power and RAM. Problem is, I started getting
an error that my database was in an unrecognized format. That has happened
about 3 times, the first one made me lose about 3 weeks worth of tickets
(the DB is running a Delivery Ticket system). Now I am getting an error
that the database needs to be repaired. I have to get everyone out and so
far have been able to compact and repair with no problem.
Is there anyone out there with ideas of why this is happening and how to
stop it? I am worried that I am gonna get caught with by data drawers
down.....
Thanks in advance for any assistance you can render....
推荐答案
你推的最大尺寸（2GB）？我们有一个数据库做了同样的事情，不得不每天2次压缩，这是因为它只是2GB的b $ b。
当你的数据库失败时，你应该将表导入一个空的
数据库，然后从备份添加表单/报告/查询，你
不会丢失任何东西。
Jamie写道：
Are you pushing the maximum size (2GB)? We had a database that did the
same thing, had to be compacted 2x daily, and it was because it was
just short of 2GB.
When your DB failed, you should have imported the tables into an empty
database and then added the forms/reports/queries from a backup, you
wouldn''t have lost anything.
Jamie wrote:
问候语！
我希望有人可以解决我遇到的问题。我有13个用户
在Access 2000上运行各种PC上的FE和新HP服务器上的BE
与Windows 2003，充足的电量和RAM。问题是，我开始得到
一个错误，我的数据库是一个无法识别的格式。这已经发生了大约3次，第一次让我失去了大约3周的票价
（DB正在运行一个交付票系统）。现在我收到一个错误
数据库需要修复。我必须让每个人都出去，所以
远远不能紧凑和修理没有问题。
有没有人在那里想到为什么这个正在发生如何
阻止它？我担心我会被数据抽屉抓住
下来.....
提前感谢您提供的任何帮助...... ..
Greeting!
I hope someone can shine a light on a problem I am having. I have 13 users
on Access 2000 running FE from various PC and the BE on a new HP Server
with Windows 2003, plenty of power and RAM. Problem is, I started getting
an error that my database was in an unrecognized format. That has happened
about 3 times, the first one made me lose about 3 weeks worth of tickets
(the DB is running a Delivery Ticket system). Now I am getting an error
that the database needs to be repaired. I have to get everyone out and so
far have been able to compact and repair with no problem.
Is there anyone out there with ideas of why this is happening and how to
stop it? I am worried that I am gonna get caught with by data drawers
down.....
Thanks in advance for any assistance you can render....
Jamie，这里有一个问题需要修复。
起点是确保修理完成了。名称自动更正
必须在后端和前端都关闭。反编译。并且可能
将所有内容导入新数据库，根据本文中的第一个症状：
http://allenbrowne.com/ser-47.html
其次，验证每个用户是否有单独的副本前端（即
他们实际上并没有使用相同的mdb前端。）
接下来，查看相当冗长的列表：
预防腐败
at：
http://allenbrowne.com/ser-25.html
确保每个人都使用MDE。
如果你是在此之后仍然卡住，记录您的用户进出，以便您可以确定哪些计算机/用户/网络连接正在脱落，并且
损坏数据。
-
Allen Browne - 微软MVP。西澳大利亚州珀斯。
访问用户提示 - http：// allenbrowne.com/tips.html
回复群组，而不是mvps dot org的allenbrowne。
Jamie < it ********* @ cox.netwrote in message
news：Xn ********************* *************@216.77.1 88.18 ...
Jamie, there is a problem here that needs fixing.
Starting point would be to ensure the repairs are complete. Name AutoCorrect
must be off in both the back end and the front ends. Decompile. And probably
import everything into a new database, as per first symptom in this article:
http://allenbrowne.com/ser-47.html
Secondly, verify that each user has a separate copy of the front end (i.e.
they are not actually using the same mdb front end.)
Next, check out the rather lengthy list in:
Preventing Corruption
at:
http://allenbrowne.com/ser-25.html
right through to ensuring everyone is using an MDE.
If you are still stuck after that, log your users in and out so you can
identify which computer/user/network connection is falling off and
corrupting the data.
--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.
"Jamie" <it*********@cox.netwrote in message
news:Xn**********************************@216.77.1 88.18...
问候语！
我希望有人能够解决我遇到的问题。我有13个用户
在Access 2000上运行各种PC上的FE和新HP服务器上的BE
与Windows 2003，充足的电量和RAM。问题是，我开始得到
一个错误，我的数据库是一个无法识别的格式。这已经发生了大约3次，第一次让我失去了大约3周的票价
（DB正在运行一个交付票系统）。现在我收到一个错误
数据库需要修复。我必须让每个人都出去，所以
远远不能紧凑和修理没有问题。
有没有人在那里想到为什么这个正在发生如何
阻止它？我担心我会被数据抽屉抓住
下来.....
提前感谢您提供的任何帮助...... ..
Greeting!
I hope someone can shine a light on a problem I am having. I have 13 users
on Access 2000 running FE from various PC and the BE on a new HP Server
with Windows 2003, plenty of power and RAM. Problem is, I started getting
an error that my database was in an unrecognized format. That has happened
about 3 times, the first one made me lose about 3 weeks worth of tickets
(the DB is running a Delivery Ticket system). Now I am getting an error
that the database needs to be repaired. I have to get everyone out and so
far have been able to compact and repair with no problem.
Is there anyone out there with ideas of why this is happening and how to
stop it? I am worried that I am gonna get caught with by data drawers
down.....
Thanks in advance for any assistance you can render....
" ManningFan" < ma ******** @ gmail.comwrote在
新闻：11 ********************* @ b28g2000cwb .googlegro ups.com：
"ManningFan" <ma********@gmail.comwrote in
news:11*********************@b28g2000cwb.googlegro ups.com:
你推的最大尺寸（2GB）？我们有一个数据库做了同样的事情，需要每天2次压缩，这是因为它只需要2GB的b $ b。
当你的数据库失败时，你应该将表导入一个空的
数据库，然后从备份添加表单/报告/查询，你
不会丢失任何东西。
Jamie写道：
Are you pushing the maximum size (2GB)? We had a database that did
the same thing, had to be compacted 2x daily, and it was because it
was just short of 2GB.
When your DB failed, you should have imported the tables into an empty
database and then added the forms/reports/queries from a backup, you
wouldn''t have lost anything.
Jamie wrote:
>问候！
我希望有人可以解决我遇到的问题。我在Access 2000上有13个用户从各种PC上运行FE，并在带有Windows 2003的新HP服务器上运行FE，充足的电量和RAM。问题是，我开始收到我的数据库处于无法识别的格式的错误。这已经发生了大约3次，第一次让我失去了大约3周的门票（数据库正在运行一个交付票据系统）。现在我收到一个错误，数据库需要修复。我必须让每个人都出去，到目前为止已经能够紧凑和修复没有任何问题。
有没有人知道为什么会这样，以及如何
阻止它？我担心我会被数据抽屉拉下来.....
提前感谢您提供的任何帮助....
>Greeting!
I hope someone can shine a light on a problem I am having. I have 13
users on Access 2000 running FE from various PC and the BE on a new
HP Server with Windows 2003, plenty of power and RAM. Problem is, I
started getting an error that my database was in an unrecognized
format. That has happened about 3 times, the first one made me lose
about 3 weeks worth of tickets (the DB is running a Delivery Ticket
system). Now I am getting an error that the database needs to be
repaired. I have to get everyone out and so far have been able to
compact and repair with no problem.
Is there anyone out there with ideas of why this is happening and how
to stop it? I am worried that I am gonna get caught with by data
drawers down.....
Thanks in advance for any assistance you can render....
哦，我远不及2GB标记，可能是12MB左右。
我试图将信息导入一个新的空白数据库，但保持
收到一个错误，该数据库是一个未识别的格式。紧凑，维修
也没有转换能够做任何事情。但是很好想。
Oh, I''m nowhere near 2GB mark, maybe something like 12MB.
I did try to import the information into a new blank database, but kept
receiving an error that the db was an unrecongized format. Compact, repair
nor convert was able to do anything. Good thought, though.
这篇关于Access 2000需要每天修复的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
