Database Search
If you can't find the information using the categories below, post a question over in our WinBatch Tech Support Forum.
TechHome
ODBC
 |
- !!NEWSFLASH!!
- 1437 or 3437 Extender Load Error
- 3132 error when using DAO
- 521 Attribute string too long
- Access SQL Update
- An SQL Tutorial
- Automated ODBC Data Source creation
- Calling a MS SQL Server 2000 Stored Procedure
- Change database then Update then count rows
- Compact an Access Database
- COMPACT_DB and Password MDB Files
- Continue a SQL Query after a Warning Message from Driver
- Create a System DSN for a TXT File Problem
- Create an SQL DSN with User name and Password
- DSN Connection Strings
- Execute an Oracle stored procedure
- Explanation of ODBC Usage
- Get Installed Driver Information
- Get Parameters from a Stored Procedure
- How Does qBindCol Work
- How to Do a Simple Sql Query
- Invalid Cursor State Error
- MDAC Invalid Object
- Microsoft SQL Server ODBC driver Info
- More on How ODBC Works
- ODBC and Services
- ODBC and SQL
- ODBC DSN Maker
- ODBC DSN Port Configuration
- ODBC Extender with WebBatch problems
- ODBC on 64 bit System
- ODBC SQLDescribeCol Example
- ODBC WHERE Syntax Blank Data
- Pervasive SQL Syntax Error
- Problem Adding System DSN for SQL Server
- Problem Using qConfigData with the Oracle ODBC Driver
- qConnect Crashes with Exit Code -1073741571
- qExecDirect and SQL Questions
- QExecDirect Second handle issue with SQL Server Drivers
- qFetch with Empty Cell
- qFetch with qBindCol and qGetData
- qGetData 50 columns limit
- qLastCode to Check these SQL Return Codes
- Read Information from Lotus Notes
- Retrieving data after a SQL JOIN
- Return Codes in ODBC Extender
- s0022 error from SQL Server Driver
- Specify SQL Server Password in qConfigData
- SQL Server SELECT SUM Statement
- SQL SUCCESS WITH INFO
- Syntax for Insert Into Access
- Updating ODBC.INI File over the Network
- Using WildCards in an ODBC SQL Statement
Can't find the information you are looking for here? Then leave a message over on our WinBatch Tech Support Forum.
ODBC DSN Maker.WBT
Keywords: ODBC DSN Maker.WBT
What follows is a script I wrote to create ODBC DSNs automatically. I used CallDll() and it worked without a 'hitch'. The sample script will create an ACCESS 97 blank database from scratch. By expanding the parameters it should be straightforward to create system or user DSN's which point to the blank file just created.
Notice I referred to DBV3 in my CREATE statement as undocumented. This has to do with the MDAC 2.1 drivers (4.x) where the default in the driver manager is for a 4.x version of ACCESS - if you use DB instead of DBV3 with 4.x drivers, you will create a blank MDB ~ 65k in size but you cannot open it with ACCESS 97.
It, of course, follows that DBV2 will create an ACCESS 2.0 compatible file.
;Winbatch - Create 'blank' ACCESS 97 Database ;Purpose - Using special call to SQLConfigDataSource() ;Author - Stan Littlefield ;param1 | Path+MDB Name ;Example:winbatch.exe sqlcfg C:\TEMP\STAN.MDB If FileExist("%param1%") == @TRUE Message("FILE ALREADY EXISTS","%param1%") exit Endif ;AddExtender("wwodb32i.dll") cDriver="Microsoft Access Driver (*.mdb)" ;Return Codes SQL_FALSE = 0 SQL_TRUE = 1 ;here are the types of operations that can be performed ODBC_ADD_DSN =1 ; Add data source ODBC_CONFIG_DSN =2 ; Configure (edit) data source ODBC_REMOVE_DSN =3 ; Remove data source ODBC_ADD_SYS_DSN =4 ; add a system DSN ODBC_CONFIG_SYS_DSN =5 ; Configure a system DSN ODBC_REMOVE_SYS_DSN =6 ; remove a system DSN cString="CREATE_DBV3=" ; undocumented feature cString=StrCat(cString,"%param1%" ) cString=StrCat(cString,Num2Char(0) ) ;add null-terminator x = DllCall("C:\WINNT\SYSTEM32\ODBCCP32.DLL", long:"SQLConfigDataSource",long:0,long:ODBC_ADD_DSN,lpstr:cDriver,lpstr:cString) If x<>SQL_TRUE Message("SQL FAILED",x) Endif
Article ID: W14775
File Created: 2001:11:08:12:39:56
Last Updated: 2001:11:08:12:39:56