MS Access FE/BE 多个表 多个链接
我在一个数据库中有一个大型复杂的多个表，客户通过某些 LAN 网络与 FE/BE 链接一起使用，这偶尔会损坏数据库
我想知道将表分组到单独的多个数据库并使用单独的链接是否有助于限制损坏？
注意：我无法控制客户的网络质量，并且大多数客户的计算机技能有限。 总的来说，一切都很好，但偶尔的故障会导致数据库损坏，这些数据库可能可以修复，也可能无法修复。
Thk 舍伍德
I have a large complex multiple table in one database that customers use with a FE/BE link over some LAN networks which occasional corrupt the database
I was wondering if grouping the tables into separate multiple databases and using separate links would help limit the damage?
Note: I have no control over customers network quality and most customers have limited computer skills.
Over all things work great but occasional glitches cause corrupt databases that may or may not be fixable.
Thk
Sherwood
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
不，将表移至多个 BE 会使其他区域的情况变得更糟，并且无助于解决腐败问题。
将表移动到多个 BE 中的问题将意味着无法在表之间强制执行关系完整性。此外，人们可能会试图恢复一个已损坏的 MDB，但没有意识到其他 MDB 中发生的各种更新现在将存在，而这些更新不在恢复的 MDB 中。事情很快就会变得非常混乱。
如果您无法控制网络质量，那么是时候考虑迁移到 SQL Server Express 了。这将需要管理员在网络中某处的计算机上安装。
有些人会建议使用 MySQL，但 SQL Server Express 也是免费的，并且与 Access 集成得更好。与 MySQL 相比，您可能会在新闻组等中获得更多有关 SQL Server 和 Access 的帮助。
您还应该考虑如何在没有 DBA 在场的情况下运行 SQL Server 数据库。并假设用户不知道如何进行备份。确保他们的备份解决方案能够以某种方式处理 SQL Server Express 备份或每天运行一项任务，将备份文件放置在用户备份的服务器上。或者甚至考虑在“高级用户”本地 PC 上制作一个副本，以至少帮助解决 SQL Server Express 系统上的硬盘驱动器故障。
当然，还有日常任务，例如截断日志等。我对这些日常任务几乎一无所知。
No, moving the tables into multiple BEs will make things worse in other areas and won't help with the corruption problem.
The problems with moving the tables into multiple BEs will mean relational integrity can not be enforced between the tables. Also folks will be tempted into restoring one MDB that gets corrupted not realizing that various updates that occured in other MDBs will now exist that aren't in the restored MDB. Things will get real messy very quickly.
If you have no control over the network quality then it's time to consider moving to SQL Server Express. This will require an admin to install on a computer in the network somewhere.
Some would suggest MySQL but SQL Server Express is also free and better integrated with Access. You will likely get a lot more assistance with SQL Server and Access in the newsgroups and such than you would with MySQL.
You should also think about how to run the SQL Server database without an DBA present. And assume that the users won't have a clue how to do backup. Make sure that their backup solutions will somehow handle SQL Server Express backups or run a task on a daily basis which places a backup file on a server somewhere which the users backs up. Or even consider making a copy on a "power users" local PC to at least help with hard drive failures on the SQL Server Express system.
And, of course the daily tasks such as truncating the logs, etc, etc. Such daily tasks of which I know next to nothing about.
您没有说明您使用的 Access 版本。
我曾经在 FE/BE 情况下使用 Access 97 和 Access 2003，并且遇到很多断开连接和损坏的情况。在任务关键型应用程序每天都失败或损坏数月之后，我们支付了百万美元的技术支持费用。
我们被告知对于关键任务，使用 Access 作为您的 FE，并使用其他一些 RDMS 作为您的后端。我们已经让 Oracle 运行用于其他任务，所以我们使用它。 MySQL 可以工作（免费），而且还有其他的。切换彻底解决了我们的问题。
我们的数据库大小从 5mb 到 1.2gb 不等，而且都在损坏。我们的应用程序中也有大约 20 个用户。我们还有大约 45 个应用程序。我对所有这些都进行了千年虫修复，这真是太麻烦了！
如果您还有其他需要，请联系他们......
You dont say what version of Access you are using.
I used to use Access 97 and Access 2003 with a FE/BE situation and I have a lot of disconnects and corruptions. We paid for M$ technical support after many months of mission critical apps just failing or getting corrupt daily.
What we were told was for mission critical, use Access as your FE and some other RDMS as your backend. We already had Oracle running for other things so we used that. MySQL would work (free) and there are others still. Switching solved our issues completely.
Our databases were anywhere from 5mb to 1.2gb and they all were getting corrupt. We did also have about 20 users in the apps too. We have about 45 apps as well. I did Y2K on all of these What a drag that was!
Hit em up if you need anything else....