How to solve OLEDB not registered in local machine

Question

0.00/5 (No votes)

See more:

Oledb access is ok when execution with IDE .... but this code is copy to paste in notepad file and save with .cs extension and compile with cmd ... this error detect..

C#

using System;
using System.Data;
using System.Data.OleDb;
using System.Xml.Serialization;


namespace MSAccessTest
{
   
   

    public class MainClass
    {
        public static void Main()
        {
            
            string cnn = @"Provider=Microsoft.ACE.OLEDB.12.0;Data Source=D:\lovetest.accdb;Persist Security Info=False";
           
            Console.Write("Enter Your Name :");
            string accName = Console.ReadLine();
            Console.Write("Enter Your Love :");
            string accNumber = Console.ReadLine();
            Random percent = new Random();

            int per = percent.Next(20, 99);

            OleDbConnection conn = new OleDbConnection(cnn);
            OleDbCommand cmd = new OleDbCommand();
            cmd.CommandType = CommandType.Text;
            cmd.CommandText = "INSERT INTO love([ID],[YourName], [YourLover],[LovePercent]) Values('"+Guid.NewGuid()+"','" + accName + "','" + accNumber + "','" + per + "')";
            cmd.Connection = conn;
          
            conn.Open();
           

            cmd.ExecuteNonQuery();
            Console.WriteLine("Your score have {0} %",per);
            conn.Close();
}
}
}

What I have tried:

I want to know MS access can connect with my c# code file without IDE.

Posted 6-Dec-17 22:36pm

Member 9998945

Updated 7-Dec-17 0:18am

Richard MacCutchan

v2

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)

OriginalGriff · Answer 1 · 2017-12-06T22:53:00

Simple: the ACE engine must be installed and registered on the machine.
If this is a different PC from that with Visual Studio installed, then install and register the appropriate version of ACE - if your app is built for 64 bit, you need 64 bit ACE, and if it's a 32 bit app, you need the 32 bit ACE engine registered.

If it's the same PC, then probably you are building it for the wrong target: 32 bit instead of 64 or vice versa. Check your IDE build properties to find out which version it builds for and include that in your command line parameters for your "manual" build.

But do yourself a favour, and don't do it like that! Never concatenate strings to build a SQL command. It leaves you wide open to accidental or deliberate SQL Injection attack which can destroy your entire database. Use Parametrized queries instead.

When you concatenate strings, you cause problems because SQL receives commands like:

SQL

SELECT * FROM MyTable WHERE StreetAddress = 'Baker's Wood'

The quote the user added terminates the string as far as SQL is concerned and you get problems. But it could be worse. If I come along and type this instead: "x';DROP TABLE MyTable;--" Then SQL receives a very different command:

SQL

SELECT * FROM MyTable WHERE StreetAddress = 'x';DROP TABLE MyTable;--'

Which SQL sees as three separate commands:

SQL

SELECT * FROM MyTable WHERE StreetAddress = 'x';

A perfectly valid SELECT

SQL

DROP TABLE MyTable;

A perfectly valid "delete the table" command

SQL

--'

And everything else is a comment.
So it does: selects any matching rows, deletes the table from the DB, and ignores anything else.

So ALWAYS use parameterized queries! Or be prepared to restore your DB from backup frequently. You do take backups regularly, don't you?