Click here to Skip to main content
13,765,005 members
Rate this:
Please Sign up or sign in to vote.
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..
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;

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

What I have tried:

I want to know MS access can connect with my c# code file without IDE.
Posted 6-Dec-17 23:36pm
Updated 7-Dec-17 1:18am

1 solution

Rate this: bad
Please Sign up or sign in to vote.

Solution 1

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:
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:
SELECT * FROM MyTable WHERE StreetAddress = 'x';DROP TABLE MyTable;--'
Which SQL sees as three separate commands:
SELECT * FROM MyTable WHERE StreetAddress = 'x';
A perfectly valid SELECT
A perfectly valid "delete the table" command
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?

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

  Print Answers RSS
Top Experts
Last 24hrsThis month

Advertise | Privacy | Cookies | Terms of Service
Web01-2016 | 2.8.181114.1 | Last Updated 7 Dec 2017
Copyright © CodeProject, 1999-2018
All Rights Reserved.
Layout: fixed | fluid

CodeProject, 503-250 Ferrand Drive Toronto Ontario, M3C 3G8 Canada +1 416-849-8900 x 100