简体繁体 English

对于MS Access / SQL Server连接，ODBC是否有替代方法？

[英]Are there alternatives to ODBC for MS Access/SQL Server Connection?

原文 2013-02-28 16:03:37 1 3 sql-server/ ms-access/ odbc/ ascii

My question is this: Are there alternatives to ODBC that would allow us to connect our SQL Server to MS Access? 我的问题是：是否有ODBC替代品可以使我们将SQL Server连接到MS Access？

Here's the situation: My company works with a proprietary, SQL database (ProVenue) that up and decided to "no longer support ODBC" to MS Access, our front-end tool, without telling us. 情况是这样的：我的公司使用专有的SQL数据库（ProVenue），并且决定不向我们的前端工具“ MS Access”“不再支持ODBC”。

We are currently migrating away from ProVenue, but in the meantime , we're stuck with a vendor, which "no longer supports" our ODBC connection(s). 我们目前正在从ProVenue迁移，但是与此同时，我们受困于供应商，该供应商“不再支持”我们的ODBC连接。 The vendor also has no incentive to help since we're leaving in several months. 由于我们将在几个月后离开，因此卖方也没有动力来提供帮助。

I've devised a workaround where I manually export the ProVenue tables (ASCII), proof (yes, the export utiliy pulls unreliably), convert and upload on a daily basis into Access. 我设计了一种解决方法，在该方法中，我手动导出ProVenue表（ASCII），证明（是的，导出工具不可靠地提取），每天转换并上传到Access中。 That said, it is unreasonably time consuming given the number of tables. 也就是说，鉴于表的数量，这是不合理的耗时。 This work-around could be a full-time job. 此变通办法可能是全职工作。

Do you know of any alternatives? 您知道其他选择吗？

3 个解决方案

Do NOT consider using ADP. 不要考虑使用ADP。 It has been dropped from Access 2013 and hence is a technology with no future. 它已从Access 2013中删除，因此是一项没有前途的技术。

From what you're saying, you don't "own" your own MSSQL database - you're simply connecting to an instance that the provider manages, correct? 用您的话说，您不是“拥有”自己的MSSQL数据库-您只是连接到提供者管理的实例，对吗？ I would guess that they've disabled ODBC connections to MSSQL because they don't like the load placed on their servers and/or that they've decided they want to change some underlying structures and don't want to have to cope with anybody whining about those changes. 我猜他们已经禁用了与MSSQL的ODBC连接，因为他们不喜欢服务器上的负载，并且/或者他们决定更改某些基础结构，并且不想与任何人打交道。抱怨那些变化。

That said, do they allow direct MSSQL connections? 也就是说，它们是否允许直接MSSQL连接？ Via SQL Management Studio, for example? 例如通过SQL Management Studio？ If so, you should be able to define an export & import process which is less buggy than theirs, and simply re-point your Access database to the local copy of data. 如果是这样，您应该能够定义一个比其错误少的导出和导入过程，并且只需将Access数据库重新指向数据的本地副本即可。 True, this would still require some (possibly automated) import process, so you'd be out of synch with the server, but it'd give you the solution. 没错，这仍然需要一些（可能是自动化的）导入过程，因此您将与服务器不同步，但这将为您提供解决方案。

You might try connecting an .adp file to the server, to see if they'll still let you access things in that manner. 您可以尝试将.adp文件连接到服务器，以查看它们是否仍然允许您以这种方式访问内容。 That would possibly require significant modifications to your Access solution, but would also be a bit easier on their servers than linked tables via ODBC. 这可能需要对Access解决方案进行重大修改，但是在它们的服务器上比通过ODBC链接表要容易一些。

You could have a look at Access Data Projects (ADP) which are tied directly to one SQL Server database. 您可以查看直接与一个SQL Server数据库绑定的Access Data Projects（ADP）。 I don't think they use ODBC at all, but they have their own limitations, and of course, aren't available in older Access versions. 我认为它们根本不使用ODBC，但是它们有其自身的局限性，当然，在较早的Access版本中也不可用。