An application written using ODBC can be ported to other platforms, both on the client and server side, with few changes to the data access code.ODBC accomplishes DBMS independence by using an ODBC driver as a translation layer between the application and the DBMS.Stata's odbc command allows you to load, write, and view data from Open Data Base Connectivity (ODBC) sources.Before you start using the odbc command in Stata, you must first set up a data source name (DSN) in the ODBC Data Source Administrator.And this is for ANY application, name it PHP, Coldfusion, whatever2.You cannot make a system DSN with a UNC (\Server\resource), so you must map the drive Cute isn't it? I quit on ODBC and went via ADO, this is the code that works:=== CODE ===$db = '\\server\resource\db.mdb';$conn = new COM('ADODB.All I got is this message: Warning: SQL error: [Microsoft][ODBC Microsoft Access Driver] '(unknown)' is not a valid path.Make sure that the path name is spelled correctly and that you are connected to the server on which the file resides., SQL state S1009 in SQLConnect in d:\apache\cm\on line 13So...
Before you install an ODBC driver, you need to determine whether your SQL client tool is 32-bit or 64-bit.
Setting up a DSN differs slightly depending on your version of Windows: Windows 8 or Vista or Windows 7. If you encountered any problems during the setup process, there are some troubleshooting tips below.
Now that you have set up your DSN, open Stata, and type odbc list in the Stata Command window.
I started looking al around and looks like the ODBC driver has some severe problems:1.
It cannot access a Access database via a mapped drive.
I'm quite familiar with VBA but have never had to deal with SQL servers/tables until now.