oledb

I can't seem to read a .csv file using the following connection string: var fileName = string.Format("{0}{1}", AppDomain.CurrentDomain.BaseDirectory, "Uploads\\countrylist.csv"); string connectionString = string.Format(@"Provider=Microsoft.Jet.OLEDB.4.0; Data Source={0}; Extended Properties=""text;HDR=YES;FMT=Delimited""", fileName); OleDbConnection oledbConn = new OleDbConnection(connectionString); oledbConn.Open(); It gives the following error: 'D:\arrgh\arrgh\Uploads\countrylist.csv' is not a valid path. Make sure that the path name is spelled correctly and that you are connected to the

For debugging purpose I'd like to know ways to test OLE DB connection string quickly. I've found this free software , it works on my machine, tested successfully. Is there a even quicker way to do so, maybe from command line on Windows? Because most of the time, it is the client rather than me that would do this task, so I prefer a "zero-installation" approach that would impact their system the least. If the client has PowerShell installed (a given if they are running Windows 7 or Windows Server 2008 R2), then you can execute these commands from a PowerShell console window: $conn = New-Object

This question already has an answer here: what is the difference between OLE DB and ODBC data sources? 11 answers What is the difference between OLEDB and ODBC? When do I use which and how do I know what I am looking at is a OLEDB driver v/s an ODBC driver? OLEDB and ODBC are two different database API's. ODBC is an older standard and is actually not specific to windows - you can get Unix-based ODBC libraries. OLEDB is a COM-based API for database connections. There is a driver for wrapping ODBC with an OLEDB front-end if the database you are using does not come with a native OLEDB driver.