ADODB或OLEDB用于快速桌面应用程序

本文介绍了ADODB或OLEDB用于快速桌面应用程序的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！ 问题描述

Hello Team， 我正在开发桌面应用程序并使用1. C＃WindowsFormsApplication和MS Access DataBase作为后端。 我的应用程序将在一分钟内插入大约60-70条记录。 所以请建议 - 应该我使用 - OLDDB或ADODB连接？ - 在客户端计算机上没有安装MS Access，哪个连接可以工作 - 如果客户端操作系统是32位且MS办公室是64位然后连接将有所帮助 感谢提前帮助!!! 谢谢， Pravin K

Hello Team, I am developing desktop application and using 1. C# WindowsFormsApplication & MS Access DataBase as backend. My Application is going to insert around 60-70 records in a minute. So Please suggest - should I use - OLDDB OR ADODB connetions? - Without MS Access installed on client machine, which connection will work - If client OS is of 32 Bit and MS office is of 64 Bit then connection will help anyway Thanks for the help in advance!!! Thanks, Pravin K

推荐答案

您尚未指定是否有多个客户端（通过网络传播）访问同一数据库。但根据你所写的内容，我认为是这种情况。 我绝不会出于任何原因使用Access作为后端，特别是当它与并发连接有关时。 Microsoft Access不是作为客户端 - 服务器架构设计的，它对共享的支持有限，特别是因为一切都取决于客户端。它可以处理每分钟60-70次插入，但我不相信它与关键数据。 所以我的建议是： 如果数据库只有一个客户端，并且数据库与它位于同一台机器上：切换到SQLite。 如果您有多个客户端，请使用真实客户端 - 服务器体系结构，如：SQL Server Express版本，如果10GB数据库足够，Firebird，MySQL，DB2 Express，Oracle Express ......等等。 You have not specified if there will be more than one clients (spread over a network) accessing the same database. But based of what you wrote, I assume this is the case. I would never use Access as backend for any reason, especially when it is about concurrent connections. Microsoft Access is not designed as a client-server architecture, it has limited support of sharing, especially because everything depends on the client. It could handle those 60-70 inserts per minute, but I wouldn't trust it with critical data. So my suggestion is: If you have only a single "client" for the database, and the database resides on the same machine with it: switch to SQLite. If you have multiple clients, use something with real client-server architecture, like: SQL Server Express edition if 10GB database is enough, Firebird, MySQL, DB2 Express, Oracle Express... and many others.