MS Access 2003 - 帮助理解mdb、mde和be的结构
我只是想解释一下，一旦您将表拆分成后端文件，并设置 mde 供使用，会发生什么情况。
当用户访问 mde 时，mdb 是否仍然需要访问 tabes（或者为了使其工作）？假设我将这些访问应用程序放在共享驱动器上供人们使用。如果我将 be end 拆分到共享驱动器上，并将 mde 放在共享驱动器上，那么 mdb 是否必须存在才能使该版本的 mde 工作（与表通信）？或者 mde 是否与 mdb 通信，mdb 与表通信？
希望这个问题有意义。
谢谢
编辑：
还有一个问题：我在网络共享驱动器上设置了 MDE，但我不确定是否必须将 mdb 与我的 mde 和后端（表）放在同一共享驱动器上....如果没有，那么我宁愿不在那里，因为用户坚持要进入它，并制作它的副本等等...
但我的问题是，正如我所说，我将 MDE 放在了共享驱动器，这意味着最多有 10-12 人共享驱动器，而即使其中一半的人同时在那里也是非常不现实的。但我最近读到我应该为每个人都有一个 MDE？这是真的吗？向每人分发一份的好例子是什么？我以前只在共享方法上使用过这个方法，并且没有意识到这是一种糟糕的方法（如果事实上是的话）？
感谢您的帮助！
I was just wanting some explanation as to what is going on once you have split your tables out into a back end file, and set an mde out for use.
When a user accesses the mde, is the mdb still required to get to the tabes (or in order to make it work)? Let say I put these access apps on a shared drive for folks to use. If I split the be end on to the shared drive, and placed the mde on the shared drive, would I the mdb have to exist for that version mde to work (communicate with the tables)? Or does the mde sort of speak to the mdb which speaks to the tables?
Hope this question makes sense.
Thanks
EDIT:
One additional question: I have an MDE set up on a network share drive, but I was not certain as to whether or not I had to have the mdb present on the same share drive as my mde and back end (tables)....if not then I would prefer to not have it there because user insist on getting into it, and making copies of it and such.....
But my question is, as I said I put A MDE out on a shared drive, which means there is one that about 10-12 people max, share, and the likelihood that even half these folks would be in there at the same time is very very unrealistic. But I recently read that I should have an MDE for each person? Is that true? What is a good example of distributing one to each person? I have only ever gone with the one on a shared appraoch before, and was unaware that this was, if in fact it is, a bad approach?
Thanks for your help!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
否，MDE 版本不与其原始 MDB 源版本保持任何通信。但是，您希望将 MDB 保存在安全的位置，以便可以在那里进行设计更改，然后从更新的 MDB 创建新版本的 MDE。
MDE 的更强有力的情况是针对您分发给用户的前端应用程序 -- 假设您不希望他们更改任何数据库对象的设计。后端数据库传统上仅包含表、关系和索引。您可以决定后端可以保留 MDB 格式。
编辑：不允许允许您的用户打开相同的前端应用程序数据库，无论前端是MDE还是MDB格式。共享相同的前端会增加腐败的风险。它们仍然可以共享相同的后端，并具有从前端到后端表的链接。
Tony Toews 使为每个用户提供自己的前端本地副本的挑战变得相当容易。请访问 Auto FE Updater 查看他有用的且免费！实用程序。
No the MDE version does not maintain any communication with its original MDB source version. However you want to keep the MDB in a safe place so you can make design changes there, and then create a new version of the MDE from the updated MDB.
The stronger case for an MDE is for the front end application you distribute to your users --- assuming you don't want them changing the design of any database objects. The back end database traditionally contains only tables, relationships, and indexes. You may decide the back end can remain in MDB format.
Edit: Do not allow your users to open the same front end application database, regardless of whether the front end is in MDE or MDB format. Sharing the same front end increases the risk of corruption. They can all still share the same back end with links from the front end to the back end tables.
Tony Toews has made the challenge of giving each user their own local copy of the front end fairly easy. See his useful and free! utility at Auto FE Updater.
@HansUp 在回答你的实际问题方面做得很好，但我在这里发布一个答案只是为了试图解释一下是什么让你感到困惑。
退后一步，考虑一下 Microsoft Word 是如何部署和编程的。
当您在计算机上安装 Word 2007 时
计算机，您不与其共享它
其他用户——你们每个人都安装
在您自己的 PC 上。
当你安装它时，你
安装编译的应用程序，
不是源代码。
Microsoft 保留并维护
源代码，您不需要
在您的 PC 上运行 Word。
Word 的源代码就像
前端 MDB。
编译后的Word EXE及其所有内容
支持文件就像
前端 MDE。
就像使用 Word 应用程序一样
文件，您不共享它，而是给予
每个用户都有一份单独的副本。
与 Word 一样，您的用户不需要
运行编译后的源代码
应用程序，所以您的所有用户都需要
是 MDE。
就像微软一样，你需要采取
照顾你的源代码MDB，以便
它不会被损坏或丢失，
以便您可以继续更新
它并产生新的编译版本
为您的用户。
当你了解了不同部分的功能和作用后，事情并不复杂。这是令人困惑的，因为 MS 的 Access 文档往往不会推广或解释最佳实践。我不太明白为什么这么久之后还是这样，但仍然如此。
不过，你已经在正确做事的路上了。
@HansUp has done a fine job of answering your actual questions, but I'm posting an answer here just to try to explain what seems to have confused you.
Step back for a moment and consider how Microsoft Word is deployed and programmed.
When you install Word 2007 on your
computer, you don't share it with
other users -- each of you installs
it on your own PCs.
When you install it, you're
installing the compiled application,
not the source code.
Microsoft keeps and maintains the
source code, which you don't need to
run Word on your PC.
The source code for Word is like the
front-end MDB.
The compiled Word EXE and all of its
supporting files is like the
front-end MDE.
Just as with the Word application
files, you don't share it, but give
each user an individual copy of it.
As with Word, your users don't need
the source code to run the compiled
application, so all your users need
is the MDE.
Just like Microsoft, you need to take
care of your source code MDB so that
it doesn't get corrupted or lost, in
order that you can continue to update
it and produce new compiled versions
for your users.
It's not complicated when you understand the function and role of the different parts. It is confusing because of the fact that MS's documentation for Access tends not to promote or explain best practices. I can't quite understand why this is the case after all this time, but it still is.
You're well on the way to doing things properly, though.