odbc

I'm trying to connect to SQL server 2000 installed on Windows server 2003 from Windows Server 2008 R2 using Python 3.4 and pyodbc module. Those servers are in different AD domains. Windows only authentication is enabled on SQL server and I can't change that. drv = '{SQL server}' svr = 'sql.my-domain.local' usr = 'my-domain.local\testuser' pwd = 'password' db = 'testdb' pyodbc.connect(driver=drv, server=svr, user=usr, password=pwd, database=db) The connection above fails with the following error: pyodbc.Error: ('28000', "[28000] [Microsoft][ODBC SQL Server Driver][SQLServer] Login failed for

I found this question here: OLEDB v/s ODBC Which gave me more information, but did not really answer the question I'm asking, so I shall proceed from there. I am working in C#. I'll spare you the long story about how I arrived at this conundrum, but basically I'm trying to decide between ODBC and oleDB. We work with a lot of different clients who have vastly varied Databases (some SQL, some oracle, some something else that I've never heard of and didn't bother to remember the name of) Now, from what I understand, ODBC is old, and was/is the standard. And now OleDB has come along and... is...

I'm using ArchLinux and I am trying to install OpenEdge progress drivers so I can access it via PHP. I've installed the unixodbc package and the drivers, but when I test the connection via isql or PHP, I get the same error... # isql -3 SUBS2A [01000][unixODBC][Driver Manager]Can't open lib '/usr/dlc/odbc/lib/pgoe1023.so' : file not found [ISQL]ERROR: Could not SQLConnect The messed up thing is that "/usr/dlc/odbc/lib/pgoe1023.so" presently exists, I even symlinked it from "/usr/dlc". The following are my .ini files... odbc.ini [SUBS2A] Description = ODBC Driver for Progress Driver = /usr/dlc

I have googled for hours now. I have read countless articles such as: Is there a Windows 7 ODBC driver for Access? I have tried using both the ODBC admin - and have managed to successfully add there system DSN for both: Microsoft Access Database Microsoft do Access Database When I attempt to connect to Access DB stored locally: odbc_connect('Aquarius2', '', ''); I get the following error(s): odbc_connect(): SQL error: [Microsoft][ODBC Driver Manager] The specified DSN contains an architecture mismatch between the Driver and Application, SQL state IM014 in SQLConnect in C:\export\export.php on

Is it possible to make query like SELECT from VBA in Excel, so I can query a PostgreSQL DB from Excel? If is possible please explain me how to connect to the database. I was looking in Google but found no results. Craig Ringer Create a table or view in PostgreSQL that describes the data you want. Use an ODBC or ADO connection from VBA to connect to PostgreSQL. If using ODBC you'll need to create a DSN via odbcad32.exe then use the DSN in VB, it isn't easy to just connect directly. See: Using ADO in VBA to connect to PostgreSQL PostgreSQL Query to Excel Sheet http://jackdebear.blogspot.com.au

[edit] We're collecting credit application data from users on a web form. I have not tied my web form directly into QB. I have no idea what the QB table structure is for this collection of data - nor of how it displays it to the user because I've never actually worked directly with QB. Others in my office do however. I would still appreciate any information about open source / free options. I'll simplify the problem by removing the first desired option. Let's just talk about importing a flat file into quickbooks. I don't have a copy of quickbooks that I can play with, so I have no idea what

I created a Delphi application which utilizes an ODBC data source to access text files in csv format. The driver is the "Microsoft Access Text Driver". But when I deploy my application on a Windows 7 computer it does not work because this driver is not available (there are only two available in odbcad32: sql native client and sql server) How can I install this driver? I have tried to install MDAC, but it doesn't do anything. No errors or anythinig, but it just shows a quick scroll bar and that is it. And I have heard that MDAC has been replaced by WDAC on Windows 7. EDIT: I should add this is

I currently have an MS Access application that connects to a PostgreSQL database via ODBC. This successfully runs on a LAN with 20 users (each running their own version of Access). Now I am thinking through some disaster recovery scenarios, and it seems that a quick and easy method of protecting the data is to use log shipping to create a warm-standby. This lead me to think about putting this warm-standby at a remote location, but then I have the question: Is Access connecting to a remote database via ODBC usable? I.e. the remote database is maybe in the same country with ok ping times and I

I have an SQL Server database, and I need to push data into it through vbscript, as well as pull data into Excel. I have found multiple connection strings, but no repository for the benefits of performance and functionality comparing them. The driver options ( Provider= ) I have found so far are: {SQL Server} (ODBC) SQLOLEDB (newer than ODBC, but being deprecated ?) SQLOLEDB.1 (what Excel 2016 uses when clicking 'Get External Data', but not even mentioned on connectionstrings.com... I assume a newer version of the above, but still the deprecated technology?) SQLNCLI11 (native client, OLE DB)

I am trying to transfer bulk data on a constant and continuous based from a SQL Server database to a MYSQL database. I wanted to use SQL Server's SSMS's replication but this apparently is only for SQL Server to Oracle or IBM DB2 connection. Currently we are using SSIS to transform data and push it to a temporary location at the MYSQL database where it is copied over. I would like the fastest way to transfer data and am complication several methods. I have a new way I plan on transforming the data which I am sure will solve most time issues but I want to make sure we do not run into time