在 Access 2007 中重建 Access adp 并出现错误
我正在尝试在 Access 2007 中重建 Access adp 应用程序。我从一个空白数据库开始，使用 ODBC 链接我需要的 SQL Server 表，然后复制原始应用程序中的所有表单。然后，我更新了表单的数据源以转到正确的表。
当我打开其中一个表单时，收到错误“WITH OWNERACCESS OPTION 声明中的语法错误”。此错误是在运行 Open 事件代码之前发生的。
有谁知道如何追踪此错误的来源？或者也许有另一种方法来完全做到这一点？
谢谢！
I'm trying to rebuild an Access adp application in Access 2007. I started with a blank database, linked the SQL Server tables I need with ODBC, and then copied over all of the forms from the original application. I then updated the data sources for the forms to go to the correct tables.
When I open one of the forms, I get the error "Syntax error in WITH OWNERACCESS OPTION declaration". This error is occurring before the Open event code is being run.
Does anyone have any ideas about how to track down where this error is coming from? Or maybe an idea of another way to do this altogether?
Thanks!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
WITH OWNERACCESS OPTION 在 ADP 中没有任何意义，因为它是 Jet SQL 与 Jet 用户级安全性一起使用的命令。对于ADP，安全性应该全部在服务器上设置。因此，您应该从表单 RecordSources 中删除所有WITH OWNERACCESS OPTION 语句。
坦率地说，我不确定它们除了保存的 QueryDef 之外还有什么影响，所以它们很可能是原始应用程序中的错误。
另外，我绝不会建议将 MDB 中的任何内容复制到 ADP 中。首先，我不认为迁移到 ADP 是明智的（尽管我确实使用 ADP 作为使用 SQL Server 的 MDB/ODBC 应用程序的管理工具），但其次，这两个平台之间存在如此多的差异，我只是看不到他们工作。
如果我选择将 MDB 迁移到 ADP（我无法想象我会这样做，因为 MS 已经弃用 ADP 大约五年了），我会从头开始并从头开始重建它。
WITH OWNERACCESS OPTION makes no sense in an ADP, as it's a command for Jet SQL for use with Jet user-level security. With an ADP, the security should all be set on the server. So, you should remove all the WITH OWNERACCESS OPTION statements from your form RecordSources.
Frankly, I'm not sure they have an effect in anything other than a saved QueryDef, so likely they were an error in the original application.
Also, I would never recommend copying anything from an MDB into an ADP. First off, I don't believe migrating to an ADP is ever advisable (though I certainly use ADPs as an administrative tool with my MDB/ODBC apps that use SQL Server), but secondly, there are so many differences between the two platforms that I just can't see them working.
If I chose to migrate an MDB to ADP (and I can't imagine that I ever would, given that MS has been deprecating ADPs for about half a decade now), I would start from scratch and rebuild it from the ground up.