访问性能与.Net性能 [英] Access Performance Vs .Net Performance

问题描述

我提出的问题是那些曾参与过Access编程的人，然后转到.Net FrameWork（C＃visual Studio）



如果我们有一个应用程序需要插入更新和删除操作

如果我们在C＃.net和Access中部署它有什么好处？

或没有区别？

i认为速度是差异

那么什么是c＃.net优势 s vs Access？

解决方案

< blockquote>请注意，我自己并没有使用MS Access，而且我唯一的体验就是多年前与Excel进行了一些互操作。



在部署方面：MS确实提供免费的MS Access运行时间（无需购买）： ^ ]，[ ^ ]。


在速度方面：取决于数据库的结构，用例等。



我建议你阅读这个比较访问和SQL：[ ^ ]。

主要区别在于，如果部署基于Access的解决方案，则用户必须在其计算机上安装Access才能使用它。情况可能并非如此，并且用户修复可能会很昂贵...

另一方面，AC＃/ .NET解决方案应包括安装包中的所有相关文件，以及所以不应该依赖以前安装过软件的用户。

my question is raised to the people who have worked in Access Programing and moved then to .Net FrameWork(C# visual Studio)

if we have an application that needs insert update and delete operations
what will the advantages that it have if we deploy it in C#.net Vs Access
or there is no difference ?
i think the speed is the difference
so what are c#.net advantages vs Access ?

解决方案

Note that I do not use MS Access myself, and my only experience with it was doing some interop with Excel many years ago.

In terms of deployment: MS does provide free MS Access run-time for use (no purchase required): ^], [^].

In terms of speed: depends on the structure of the database, the use-cases, etc.

I suggest you read this comparison of Access and SQL: [^].

The major difference is that if you deploy an Access based solution, then the user has to have Access installed on his computer in order to use it. This may well not be the case, and can be expensive for the user to fix...
A C# / .NET solution on the other hand should include all the relevant files in the installation package, and so shouldn't rely on the user having software previously installed.

这篇关于访问性能与.Net性能的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！