创建前端 MDE [英] Creating the Front End MDE
问题描述
我创建了一个用于跟踪指标的数据库，其中包含一些自动化技巧(电子邮件、.doc、.ppt 演示文稿等)、一个非常大的主表和大量表单/GUI.这是我第一次为这件事担心 MDE/前端.因此，如果您愿意回答几个问题或提供任何建议，我们将不胜感激(我不希望所有这些工作都没有被利用).
I created a database for tracking metrics, with some automation tricks (email, .doc,.ppt presentations, etc) with a very large Main-table, and lots of forms/GUI. This is the first time I have ever I worried about an MDE/front-end for the thing. So if you would be so kind to answer a few questions, or offer any advice, it would be greatly appreciated (I would hate for all this work to not be utilized).
我需要做的第一件事是什么?2000 版本必须转换为 03 才能创建 MDE，但在我使用数据库拆分器之前完成了吗?
What is the first thing I need to do? It the 2000 version that must be converted to 03 to create the MDE, but does that get done before I use the database splitter?
数据库中的对象数量会影响执行此操作的能力吗?我有 80 个表单、70 个查询、20 多个宏、12 个表等……但是一旦前端出现，对象的数量是否会阻止其中的一些工作正常?
Will the amount of objects in the database effect the ability to do this? I have something like 80 forms, 70 queries, 20+ macros, 12 tables, etc...but does the amount of objects prevent some of this from working well once the front end is there?
当我拆分数据库时，我可以继续在后端"工作/进行更改等，并使这些更改直接影响前端吗?
when i split the database, can I continue to work/make changes and such on the "back end", and have those changes directly effect the front end?
这些可能是一些基本问题，但我不知道答案所以.....谢谢！
These may be some basic questions, but I don't know the answer so.....Thanks!
推荐答案
这是我的 2 ¢.
问题 1 - 我从未使用过数据库拆分器，因为我觉得我可以更好地控制手动操作.如果您手动执行此操作，则可以对没有数据库拆分器的版本执行此操作.但是，如果您确实使用了拆分器，那么-是的-您必须先升级到具有拆分器的版本，然后再使用.
Question 1 - I have never used the database splitter as I feel I have more control doing it manually. If you do it manually you can do it to a version that does not have a database splitter. But if you do use the splitter then--yes--you will have to upgrade to a version that has a splitter before doing it.
这里是手动操作的步骤.
To do it manually here are the steps.
- 备份一切.
- 在同一目录中创建文件的副本.因此，如果您有 MyApp.MDB，请使用新名称在同一目录中创建一个副本，例如 MyAppDATA.mdb.
- 打开新的数据文件 (MyAppDATA.mdb) 并删除除 TABLES 之外的所有对象.
- 打开应用程序文件 (MyApp.mdb) 并删除所有表.
- 也在 MyApp.mdb 中...转到文件/获取外部数据/链接表"菜单，将 MyAppDATA.mdb 中的表链接到 MyApp.mdb.全选并创建链接.
应该可以.如果你搞砸了，你做了一个备份......对吗?
That should do it. And if you screw up you made a backup...right?
一些提示和问题...确保您转到工具/选项"并且没有显示系统和隐藏表.您只是不想从 MyApp 中删除系统表.另一种方法是不要删除以 MSys 或 USsys 开头的表.
A couple of tips and gotchas...be sure that you go to Tools/Options and that you are NOT showing System and Hidden tables. You just don't want to delete system tables from MyApp. Another way to do it is do NOT delete tables that start with MSys or USys.
问题 2 - 与您拥有多少对象无关.事实上，无论如何你都没有那么多对象.
Question 2 - Does not matter how many object you have. In fact you don't have that many objects anyway.
问题 3 - 是的...您将在 MyAppData.mdb 中进行后端更改，当您打开 MyApp.mdb 时，这些更改将自动神奇地出现在那里以查看和查询等(在查询设计器中，您可能需要如果您在查询中创建了 mod，则保存/关闭/重新打开以查看新字段).唯一的例外是新表您必须使用文件/获取外部数据/链接表选项来创建到新表的链接.
Question 3 - Yes...you will make backend changes in MyAppData.mdb and when you open MyApp.mdb those changes will auto-magically be there to see and query against etc. (In the query designer you may need to save/close/reopen to see new fields if you made the mod while in the query). The EXCEPTION to that is New Tables You will have to use the File/Get External Data/Link Tables option to create links to new tables.
要记住的一件事(我希望您已经意识到)是拆分数据库的一个缺点是，当您部署前端文件时，通常数据的相对路径会因机器而异没有自动重新链接访问中的表.如果您的目标客户具有完全访问权限，您可以随时使用工具/数据库实用程序/链接表管理器将链接刷新到正确的位置.如果您不能这样做，那么您将必须执行以下操作之一:
1. 编写自动重新链接的代码.基本上它会检查链接...如果无效，它会提示用户输入数据位置(或在 INI 文件中查找)并重新链接表.
2. 始终将您的应用程序部署到所有机器上的相同位置.如果您对您的应用程序有商业愿景，这将行不通……我出于学术原因提到它.对于有限的部署，您可以对每台机器上的文件放置进行大量控制，这可能是可行的.
3. 将数据文件 (MyAppDATA.mdb) 放到网络共享上，并使用驱动器映射或 UNC (myservermydataApplicationDataMyAppData.mdb) 通过网络链接该表.后者是首选，但它们都具有与第二个相同的风险.
One thing to remember (and that I hope you already realize) is that the one downside of splitting the database is that when you deploy the front end file that usually the relative path to the data will vary from machine to machine and there is no automatic re-linking of tables in access. If your target clients have full access you can always use Tools/Database Utilities/Linked Table Manager to refresh the links to the right location. If you can't do that then you will have to do one of the following:
1. Write code that does the automatic re-linking for you. Basically it will check the links...if invalid it will prompt the user for the data location (or look it up in an INI file) and re-link the tables.
2. Always deploy your app to the same location on all machines. If you have commercial visions for your application this won't work...I mention it for academic reasons. It might be doable for a limited deployment where you have a lot of control over file placement on each machine.
3. Put the Data file (MyAppDATA.mdb) onto a network share and link the table across the network using a drive mapping or UNC (myservermydataApplicationDataMyAppData.mdb). The latter is preferred but both of them run the same risks as number two.
赛特
PS 此答案假设 Access 2003.
PPS 如果您对应用程序有商业愿景，那么表链接必须非常可靠.PPPS 我同意评论者的观点，如果您的技能范围内，您可能想要尝试并执行 SQL.
PS This answer assumes Access 2003.
PPS If you have commercial visions for your application then the table linking has got to be REALLY robust.
PPPS I agree with the commenter that you may want to take the plunge and do SQL if it is in your skill set.
这篇关于创建前端 MDE的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
