当前位置：文江博客话题详情

能否将 Access 2.0 升级到 Access 2000 或更高版本的 Access 项目？

发布于 2024-07-28 23:14:40 字数 186 浏览 5 评论 0原文

由于合并，我们继承了一些在 Access 2.0 上运行的旧应用程序。理想情况下，我们希望将它们重写为 Intranet Web 应用程序，但由于其他优先事项，这不会很快发生。

我们主要关心的是从客户端计算机获取数据并最好将其放入 SQL Server。有没有办法将 2.0 升级到 Access 2000 或更高版本的项目？

原文

分享到QQ

分享到微博

如果你对这篇内容有疑问，欢迎到本站社区发帖提问参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。

发布评论

需要登录才能够评论，你可以免费注册一个本站的账号。

情深如许 2024-08-04 23:14:40

除了 Mitch 的链接之外，当您将 A2.0 转换为 A2000 或更新版本时，您可能还会得到一两个无用的参考资料。最后，您只需要以下四个参考文献。

Visual Basic For Applications 
     VBA - 4.0 C:\Program Files\Common Files\Microsoft Shared\VBA\VBA6\VBE6.DLL
Microsoft Access 9.0 Object Library 
     Access - 9.0 C:\Program Files\Microsoft Office 2000\Office\msacc9.olb
OLE Automation 
     stdole - 2.0 C:\WINDOWS\system32\STDOLE2.TLB
Microsoft DAO 3.6 Object Library 
     DAO - 5.0 C:\Program Files\Common Files\Microsoft Shared\DAO\dao360.dll

Sub ViewMoreReferenceDetails()

Dim refIDE As Object

    For Each refIDE In Access.Application.VBE.ActiveVBProject.References
        Debug.Print refIDE.Description & " " & _
            IIf(refIDE.IsBroken, "Broken", "") & vbCrLf & _
            "     " & refIDE.Name & " - " & refIDE.Major & "." & refIDE.Minor & " " & refIDE.FullPath
    Next refIDE

End Sub

当然，您的 Microsoft Access 对象库版本将根据您的 Access 版本而有所不同。即使如此，OLE 引用也不是必需的，但您最好将其留在那里。

Access 可能自动添加的兼容层引用如果有效的话，绝对应该删除。但清理它试图修复的代码应该不会花很长时间。

至于转换为 ADP，大概就是您在声明项目时的意思，Microsoft 不再推荐了。在 Access 的最近几个版本中，它没有任何新功能。相反，只需使用 SQL Server 的链接表即可。

请参阅 Microsoft Access Tips 页中我对 SQL Server 升迁的随机想法，网址为 http://www。 Granite.ab.ca/access/sqlserverupsizing.htm

SQL Server 组有一个工具。
用于访问的 SQL Server 迁移助手（SSMA 访问）
http://www.microsoft.com/sql/solutions/migration/访问/default.mspx

In addition to Mitch's links you will probably get one or two useless references when you convert the A2.0 to A2000 or newer. At the end you should only need the following four references.

Visual Basic For Applications 
     VBA - 4.0 C:\Program Files\Common Files\Microsoft Shared\VBA\VBA6\VBE6.DLL
Microsoft Access 9.0 Object Library 
     Access - 9.0 C:\Program Files\Microsoft Office 2000\Office\msacc9.olb
OLE Automation 
     stdole - 2.0 C:\WINDOWS\system32\STDOLE2.TLB
Microsoft DAO 3.6 Object Library 
     DAO - 5.0 C:\Program Files\Common Files\Microsoft Shared\DAO\dao360.dll

Sub ViewMoreReferenceDetails()

Dim refIDE As Object

    For Each refIDE In Access.Application.VBE.ActiveVBProject.References
        Debug.Print refIDE.Description & " " & _
            IIf(refIDE.IsBroken, "Broken", "") & vbCrLf & _
            "     " & refIDE.Name & " - " & refIDE.Major & "." & refIDE.Minor & " " & refIDE.FullPath
    Next refIDE

End Sub

Of course your version of the Microsoft Access Object library will vary depending on your version of Access. Even then the OLE reference isn't required much but you might as well leave it there.

The Compatibility Layer reference which Access might automatically add should definitely be removed if it even works. But it shouldn't take long to clean up the code that it attempts to fix.

As far as the conversion to ADPs, presumably that's what you meant when you state project, isn't recommended by Microsoft any more. It hasn't had any new features in the last several releases of Access. Instead just use linked tables to SQL Server.

See my Random Thoughts on SQL Server Upsizing from Microsoft Access Tips page at http://www.granite.ab.ca/access/sqlserverupsizing.htm

There is a tool from the SQL Server group.
SQL Server Migration Assistant for Access (SSMA Access)
http://www.microsoft.com/sql/solutions/migration/access/default.mspx

回复收藏 0 原文