blocks|key|2700511|text|您可以尝试Access+Reporter。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2700512|http://www.ssw.com.au/ssw/AccessReporter/Default.aspx|offset|length|2700513|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|1H|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@$D|O|E|P|1|Q]]|A|$]]|$1|F|3|-4|5|6|7|R|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|C]]]]

You can try Access Reporter.

<a href="http://www.ssw.com.au/ssw/AccessReporter/Default.aspx" rel="nofollow noreferrer">http://www.ssw.com.au/ssw/AccessReporter/Default.aspx</a>

blocks|key|165130|text|您可能会考虑Access+2010，链接文档的第3点说：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|165131|165132|几乎可以从任何地方访问您的应用程序、数据或表单。|blockquote|165133|165134|将数据库扩展到网站，以便没有Access客户端的用户可以通过浏览器打开网站窗体和报表并自动同步更改。1或者脱机使用网站数据库，对设计和数据进行更改，然后在重新连接时将其同步到SharePoint+Server2010。使用Access+2010和SharePoint+Server2010，可以集中保护您的数据，以满足数据合规性、备份和审核要求，从而为您提供更高的可访问性和可管理性。|165135|165136|--+http://www.microsoft.com/office/2010/en/access/default.aspx|offset|length|165137|entityMap|0|LINK|mutability|MUTABLE|url|http://www.microsoft.com/office/2010/en/access/default.aspx^0|0|0|0|0|0|0|3|1N|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|W|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|X|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|G|3|H|5|6|7|Z|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|10|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|11|8|@]|9|@$L|12|M|13|1|14]]|A|$]]|$1|N|3|-4|5|6|7|15|8|@]|9|@]|A|$]]]|O|$P|$5|Q|R|S|A|$T|U]]]]

You might like to consider Access 2010, point 3 of the linked document says:

<blockquote>
 Access your application, data, or
 forms from virtually anywhere.
 
 Extend your database to the Web so
 that users without an Access client
 can open Web forms and reports via a
 browser and changes are automatically
 synchronized.1 Or work on your Web
 database offline, make your design and
 data changes, and then sync them to
 Microsoft SharePoint Server 2010 when
 you’re reconnected. With Access 2010
 and SharePoint Server 2010, your data
 can be protected centrally to meet
 data compliance, backup, and audit
 requirements, providing you with
 increased accessibility and
 manageability.
</blockquote>

-- <a href="http://www.microsoft.com/office/2010/en/access/default.aspx" rel="nofollow noreferrer">http://www.microsoft.com/office/2010/en/access/default.aspx</a>

blocks|key|2700548|text|SQL+Server+Express版是免费的。它包括Reporting+Services|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2700549|http://www.microsoft.com/Sqlserver/2005/en/us/express.aspx|offset|length|2700550|您可以连接到MS+Access数据库(或具有OLEDB或ODBC连接的任何其他数据库)|2700551|对于您现有的报表，这里有一个关于如何仅将报表迁移到SQL+Server的链接(将数据保留在MS+Access中)|2700552|http://technet.microsoft.com/en-us/library/cc966391.aspx|2700553|entityMap|0|LINK|mutability|MUTABLE|url|1^0|0|0|1M|0|0|0|0|0|1K|1|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|U|8|@]|9|@$D|V|E|W|1|X]]|A|$]]|$1|F|3|G|5|6|7|Y|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|Z|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|10|8|@]|9|@$D|11|E|12|1|13]]|A|$]]|$1|L|3|-4|5|6|7|14|8|@]|9|@]|A|$]]]|M|$N|$5|O|P|Q|A|$R|C]]|S|$5|O|P|Q|A|$R|K]]]]

SQL Server Express edition is free. It includes Reporting Services

<a href="http://www.microsoft.com/Sqlserver/2005/en/us/express.aspx" rel="nofollow noreferrer">http://www.microsoft.com/Sqlserver/2005/en/us/express.aspx</a>

You can connect to the MS Access database (or any other database that you have OLEDB or ODBC connectivity for)

For your existing reports, here is a link on how to migrate just the reports to SQL Server (leave data in MS Access)

<a href="http://technet.microsoft.com/en-us/library/cc966391.aspx" rel="nofollow noreferrer">http://technet.microsoft.com/en-us/library/cc966391.aspx</a>

blocks|key|164417|text|实际上，这里给出的建议是将您的后端和数据上移到SQL+server，但保持您的前端应用程序部分在Access中。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|164418|因此，建议不要将您的应用程序迁移到SQL+server。这里的建议是只将应用程序的数据部分移动到SQL+server，但继续使用桌面访问应用程序。|164419|因此，您可以将表链接到sql+server，并继续使用access应用程序。|164420|这意味着您可以使用SQL+server报告服务，或从SQL+server中提取数据的其他基于web的界面。因此，access应用程序将直接更新该SQL服务器上的数据。|164421|这种设置工作得很好，因为您不需要在两个单独的系统之间穿梭数据。我知道有许多公司成功地将其后台数据迁移到SQL+server，目的就是为了让高管和公司经理能够在基于web的系统上查看报告。|164422|但是，他们不必丢弃或失去构建access应用程序部分所花费的投资和时间。|164423|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|P|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|Q|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|R|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|S|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|M|$]]

Actually, the suggestion being given here is to move your back and data up to SQL server , but keep your front end application part as is in Access.

So the suggestion isn’t to move your application to SQL server. The suggestion here is to move only the data part of your application to SQL server but continue to use the desktop access application.

So, you link your tables to sql server, and continue to use the access application.

What this means that is you can use SQL server reporting services, or some other web based interface that pulls the data from SQL server. So your access application will be directly updating the data on that SQL server.

This setup works well since you not tying to shuttle data between two separate systems. I know a number of companies that successfully migrated their backend data to SQL server for this very purpose of allowing the Executives and the company Managers to view reports on a web based system. 

However, they did not have to throw out or lose the investment and time they spent building the access application part.

Client has a bunch of Access databases and associated reports.

He wants to make the reports available (live, not snapshots) via a secure extranet.

He's willing to recreate the reports using a proprietary GUI if necessary, but ideally would like a solution that exports his reports "as is" to the web.

Had a look at Caspio Bridge. It's pretty slick but doesn't appear to offer grouping and summing (key requirement) without a nasty Javascript hack - seems like a rather glaring omission to me!

Any suggestions?

I'm an ASP.NET developer so if there's coding involved, an ASP.NET based solution would be preferred.

Publishing Access database reports to the web

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

客户端有一堆Access数据库和相关的报表。他希望通过安全的外联网提供报告(实时，而不是快照)。如果有必要，他愿意使用专有GUI重新创建报告，但理想情况下，他希望有一种解决方案可以将他的报告“按原样”导出到web。看一看里斯皮奥桥。它相当流畅，但似乎没有提供分组和求和(关键要求)，而没有讨厌的Javascript攻击-对我来说，这似乎是一个相当明显的遗漏！有什么建议吗？我是一个ASP.NET开发人

问将Access数据库报表发布到web
EN

回答 4

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问将Access数据库报表发布到webEN

回答 4

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问将Access数据库报表发布到web
EN