拆分MS Access数据库并将后端存储在Sharepoint中? [英] Split MS Access Database and store back end in Sharepoint?

问题描述

我有一个带有很多VBA代码的MS Access数据库.如果创建Access Web App，我将失去代码提供的功能.有什么方法可以将我的数据库表存储在SharePoint中(不在列表中)，并将它们链接到前端以保存在每台用户计算机上?

I have an MS Access database with a lot of VBA code. If I create an Access Web App I will lose the functionality provided by my code. Is there any way to store the tables of my database in SharePoint (not in lists) and link them to the front end to be kept on each users computer?

推荐答案

您可以从Access到SharePoint(或低成本Office 365)放大数据. SharePoint表现在支持关系数据，因此，当您将Access表移至SharePoint时，就支持基本"主表到子表(以及级联删除)(但是，您只能使用自动编号的PR，并且子记录(外键)必须是一长串.

You can up-size the data from Access to SharePoint (or low cost office 365). SharePoint tables now support relational data, so "basic" master to child tables (and cascade delete) is supported when you move Access tables up to SharePoint (you are however limited to PR of auto number, and child records (foreign keys) must be a long number.

根据数据的大小和行数，与将表移至SQL Server相比，上述解决方案通常更好.此设置的一个非常好的功能是您的应用程序可以在没有任何互联网连接的情况下继续运行.找到Wi-Fi等后，您的数据就会同步.

Depending on the size and number of rows of data, the above solution is OFTEN better then moving tables up to SQL server. A VERY nice feature of this setup is that your application can continue to run without any internet connection. The instant you find some Wi-Fi etc., then your data syncs.

因此，我不会取消SharePoint表的选项，因为它们可以很好地与多种Access应用程序配合使用，包括带有相关表的应用程序. 离线"模式对于那些没有互联网连接的野外笔记本电脑来说非常有用.

So I would not write off the SharePoint table’s option, as they can work VERY well with many kinds of Access applications, including ones with related tables. And the "off line" mode can be great for those laptops in the field without an internet connection.

如果运行的是Access 2013，则可以将数据表导入基于20103 Access Web的应用程序中，然后发布到Office 365，Access会将表上推到云中的SQL Azure中.像第一个建议一样，您现在可以将传统的"VBA"富前端连接到后端数据.请记住，这种方法没有离线"模式，在某些情况下，需要更多的应用程序优化才能获得良好的性能，但是与使用SharePoint表相比，表的大小和限制要高得多.

If you are running Access 2013, then you can import the data tables into a 20103 Access web based application, then publish to office 365 and Access will push the tables up into SQL Azure in the cloud. And like the first suggestion, you can now link your traditional "VBA" rich front end to the back end data. Keep in mind that this approach does not have the "off-line" mode, and in some cases more application optimization is required to obtain good performance, but the table sizes and limits are considerably higher then using SharePoint tables.

这篇关于拆分MS Access数据库并将后端存储在Sharepoint中?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！