拆分服务器托管的 Access 数据库

发布于 2024-07-29 03:29:23 字数 367 浏览 1 评论 0原文

我正在考虑构建一个 Access 数据库,该数据库将取代链接在一起的 Excel 电子表格的非常可怕的组合。 当前电子表格系统的文件位于我们的 Windows 存储服务器上,该服务器有一个到它们使用的目录的映射驱动器。 多个用户访问该系统,因为它托管库存、每种产品使用的成分以及所有产品的定价。 我相信使用数据库是一个更好的主意。 正如我所设想的那样,如果我拆分数据库,它将给我一个前端和后端。 允许多个用户同时访问和进行更改,而不会出现损坏! 呜呼!!!

它是否正确? 有人实施过这个吗? 最终用户是否觉得使用数据库足够简单? 我没有预见到任何与此相关的问题。 我读到,前端也可以位于用户计算机本地。 真/好?

有什么经验也欢迎分享!

I am looking into building an access database that will replace a very frightening combination of excel spreadsheets that are linked together. The files for the current spreadsheet system are located on our Windows Storage Server, which has a mapped drive to the directory they use. Multiple users access this system as it host inventory, ingredients used in each product and pricing for everything. I believe using a database is a MUCH better Idea. As I am visioning it, If i split the database it would give me a front and back end. allowing multiple users to access and make changes at the same time, With out Corruption! woo-hoo!!!

Is this correct? and has anyone implemented this? did the end user find using the database easy enough? any problems with this that i did not for-see. I have read that it is also possible to have the front end locally on the users computers. True/good?

Feel free to share any experiences!

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

扫码二维码加入Web技术交流群

发布评论

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

评论(2

不醒的梦 2024-08-05 03:29:23

如果设置正确,Access 对于小型办公室来说非常有效。 数据库必须被分割,每个用户都有一个前端的副本。 这并不意味着每个用户都需要完整的Access副本,运行时版本就足够了。 2007 运行时是免费的 (http ://www.microsoft.com/downloads/details.aspx?familyid=d9ae78d9-9dc6-4b38-9fa6-2c745a175aed&displaylang=en

您应该阅读此帖子,其中涉及许多误解:MS Access (JET) 适合多用户访问吗?

Access works very well for small offices, if it is set up properly. The database must be split, with each user having a copy of the front-end. This does not mean that each user needs a full copy of Access, the runtime version is sufficient. 2007 runtime is free (http://www.microsoft.com/downloads/details.aspx?familyid=d9ae78d9-9dc6-4b38-9fa6-2c745a175aed&displaylang=en)

You should read this thread that deals with many misconceptions: Is MS Access (JET) suitable for multiuser access?

霊感 2024-08-05 03:29:23

这应该转移到 StackOverflow.com,我已投票决定将其转移。

也就是说,访问和多个用户 = 随着多个用户数量的增加,灾难即将发生。 您应该认真考虑切换到 SQL Server Express 作为后端。 您可以使用 Access 表单/报告作为前端,将表链接到 SQL Express Server。

我已经做过这种类型的分裂,但我只在很少有人会同时击中它的情况下才这样做。 有一个数据库副本,其中包含所有 UI 内容(表单、报告等),并且数据位于不同的副本中,所有表都链接在一起。 它工作得相当好,但我还是不相信超过几个人同时访问它。

我将把它留给 SO 社区的其他成员(假设它已迁移)从那里开始。

This should go over to StackOverflow.com, and I've voted to move it over.

That said, Access and Multiple Users = disaster waiting to happen as the number of multiple users goes up. You should seriously consider switching over to SQL Server Express for the backend. You can use Access forms / reports for the front end, linking the tables to the SQL Express Server.

I have done this type of split, but I only do it where there are VERY few people that would hit it at the same time. There's a copy of the database that houses all the UI things (forms, reports, etc) and the data lives in a different copy, all the tables are linked together. It works fairly well, but again I would NOT TRUST ACCESS with more than a few people hitting it at the same time.

I'll leave it to the rest of the SO community (assuming it gets migrated) to go from there.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文