MS Office 97 ODE 安装向导挂起，并显示消息“未找到路径”
我有一位客户使用 Access 97 运行时来支持他们的部分产品。 理想情况下，考虑到这样做的预算，我会在此时更换那只恐龙，但今天这不是一个选择。 我不是该系统的原始作者，但正在尝试提供持续的支持。
为了将其分发给客户，他们购买了 Office 97 开发人员版工具，并且每隔几年他们就会通过其安装向导来打包新的分发版。
这次，安装向导似乎想要使用 AXDIST.EXE 执行某些操作，而是弹出一个对话框，仅显示“找不到路径”。 我在网络上找到的唯一参考资料是对一个不再存在的域的页面的一瞥，谷歌已经清除了该域的缓存，只保留了搜索结果中出现的句子。 这不足以帮助我...
（编辑：除了由 AXDIST.EXE 本身或尝试以某种方式使用 AXDIST.EXE 的安装引起的许多报告问题之外，也就是说，我们的问题是使用 ODE 安装向导创建安装包时出现的问题。它自己的文档仅在一处引用了 AXDIST，并且根本不包含“路径未找到”文本。）
（编辑2：进一步调查显示AXDIST.EXE本身并不是罪魁祸首，从安装向导的列表中删除该文件导致向导停止在列表中的下一个文件上。它停止的文件的描述与上面列出的十几个已成功处理的文件之间的差异，我猜测此时该解决方案将手动重新创建该文件。模板从头开始，如果它没有被困在一个可怕的 UI 中并以包含一堆未记录表的 Access 数据库的形式存储，这会容易得多。）
我的问题是：这次我们犯了什么错误设置向导，我们该如何修复它？
I have a customer using the Access 97 runtime to support part of their product. Ideally, given the budget to do so, I would have replaced that dinosaur by this point, but that isn't an option today. I am not the system's original author, but am attempting to provide ongoing support.
To distribute this to their customers, they bought the Office 97 Developer Edition Tools, and once every few years they go through its Setup Wizard to package a new distribution.
This time, the Setup Wizard appears to reach a point where it wants to do something with AXDIST.EXE, and instead puts up a dialog box saying only "Path not found". The only reference I've located on the web is a tantalizing glimpse of a page from a domain that no longer exists, where Google has purged the cache retaining only the sentence that appears with the search result. It isn't enough of a hint to help me...
(Edit: Aside from lots of reported issues caused by AXDIST.EXE itself, or installations that are trying to use AXDIST.EXE in some way, that is. Our issue is a problem during the creation of a setup package using the ODE setup wizard. Its own documentation only references AXDIST in one place, and does not contain the text "path not found" at all.)
(Edit 2: Further investigation reveals that AXDIST.EXE itself is not the culprit. Removing that file from the setup wizard's list caused the wizard to stop on the next file in the list. There does not appear to be any significant differences between the description of the file on which it stopped, and the dozen or so files listed above it that were successfully processed. I'm guessing at this point that the resolution is going to be manually recreating the template from scratch, which would be a lot easier if it weren't trapped inside a horrible UI and stored in the form of an Access database containing a bunch of undocumented tables.)
My question is this: What mistake did we make this time with the setup wizard, and how can we fix it?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
事实证明，该问题与安装向导中明确列出的 Access 运行时的一项功能有关，但应该留给向导来推断。
我对任何还坚持使用向导的人的一般建议是回到起点并仔细而有条理地检查所有设置。
The issue turned out to be related to a feature of the Access run time that was explicitly listed in the setup wizard, but should have been left for the wizard to infer.
My general advice to anyone also stuck with dealing with the wizard would be to go back to the start and review all the settings carefully and methodically.