ADODB or OLEDB for Fast desktop application

Question

0.00/5 (No votes)

See more:

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

Posted 7-Jul-13 7:01am

Pravinkarne.31

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

**Zoltán Zörgő** · Answer 1 · 2013-07-07T10:05:00

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.