Ôñüðïò åãêáôÜóôáóçò áñ÷åßùí ðñïÝëåõóçò äåäïìÝíùí ODBC êáôÜ ôç äéáíïìÞ åöáñìïãþí

Áõôü ôï Üñèñï ðåñéãñÜöåé ôéò áêüëïõèåò ôÝóóåñéò ìåèüäïõò ãéá íá åãêáôáóôÞóåôå ìéá ðñïÝëåõóç äåäïìÝíùí ODBC, óå Ýíáí õðïëïãéóôÞ:

• ÅãêáôÜóôáóç ôïõ ODBC
• RegisterDatabase
• API ÔÏÕ ODBC
• Ôõöëïß INI áíôéãñáöÞ áñ÷åßùí

Áðáéôïýìåíá áñ÷åßá

ÐñÝðåé íá êáôáíåìçèïýí ôá áêüëïõèá áñ÷åßá ìå ôçí åöáñìïãÞ óáò, åÜí ÷ñçóéìïðïéÞóåôå ôï ODBC. ¼ôáí ÷ñçóéìïðïéåßôå ôïí "Ïäçãü åãêáôÜóôáóçò" ãéá íá äçìéïõñãÞóåôå äéóêÝôåò äéáíïìÞò, âåâáéùèåßôå üôé ðåñéëáìâÜíïíôáé ôá áðáñáßôçôá áñ÷åßá óôç ëßóôá áñ÷åßùí. ÐñÝðåé íá åãêáôáóôáèïýí üëá ôá áñ÷åßá ðïõ ðáñáôßèåíôáé óôïí êáôÜëïãï \WINDOWS\SYSTEM.

ÐñïáéñåôéêÜ áñ÷åßá (SQL Server Þ Oracle) ÷áñáêôçñßæïíôáé ìå Ýíáí áóôåñßóêï (*).

ÔÝóóåñéò ìÝèïäïé ãéá ôçí ëÞøç DSN ðëçñïöïñßåò óå ODBC.INI êáé ODBCINST.INI

Ôá áñ÷åßá .ini áðïèçêåýïõí ðëçñïöïñßåò ó÷åôéêÜ ìå ôá ðñïãñÜììáôá ïäÞãçóçò ODBC êáé ôá áñ÷åßá ðñïÝëåõóçò äåäïìÝíùí ODBC. Ùò áðïôÝëåóìá, åßíáé ìåôáâëçôÞ--Ýíáò ÷ñÞóôçò åíäÝ÷åôáé íá Ý÷åé Þäç ôá åãêáôåóôçìÝíá óôïí êáôÜëïãï \WINDOWS. ÅÜí ï ðñïãñáììáôéóôÞò íá áíôéãñÜøåôå blindly ODBC.INI êáé ODBCINST.INI óôïí õðïëïãéóôÞ ôïõ ÷ñÞóôç, ôá íÝá áñ÷åßá åíäÝ÷åôáé íá áíôéêáôáóôÞóåé õðÜñ÷ïíôá áñ÷åßá ðñïÝëåõóçò äåäïìÝíùí.

Ïé ðáñáêÜôù ôÝóóåñéò ìÝèïäïé ðïõ ìðïñåßôå íá ÷ñçóéìïðïéÞóåôå ãéá íá ëÜâåôå ðëçñïöïñßåò DSN óôá áñ÷åßá ODBC.INI êáé ODBCINST.INI ôïõ ÷ñÞóôç.

ÅãêáôÜóôáóç ôïõ ODBC

Ãéá íá åãêáôáóôÞóåôå Ýíá ðñüãñáììá ïäÞãçóçò ODBC êáé íá äçìéïõñãÞóåôå Ýíá ÁÑ×ÅºÏ ðñïÝëåõóçò äåäïìÝíùí ODBC, ç çëåêôñïíéêÞ ôåêìçñßùóç ÂïÞèåéáò ôçò Visual Basic óõíéóôÜ íá áíôéãñÜøåôå üëá ôá ðåñéå÷üìåíá ôïõ êáôáëüãïõ \VB\ODBC óå äßóêï ðñüóèåôåò äéáíïìÞò.

Ùò ðñïãñáììáôéóôÞò, ìðïñåßôå íá êáèïñßóåôå üôé ç åéóáãùãÞ ôïõ äßóêïõ êáé åêôåëÝóôå ôï SETUP.EXE áðü ôç äéóêÝôá. ÅðéðëÝïí, ìðïñåßôå íá æçôÞóåé áðü ôï ÷ñÞóôç ãéá íá åéóáãÜãåôå ôç äéóêÝôá ODBC êáé óôç óõíÝ÷åéá ÷ñçóéìïðïéÞóôå ôçí åíôïëÞ êåëýöïõò ôçò Visual Basic óå êÝëõöïò íá SETUP.EXE.

Ï Ïäçãüò åãêáôÜóôáóçò (Setup) áíôéãñÜöåé êáé ôñïðïðïéåß SETUP1.MAK óå SETUP1A.MAK êáôÜ ôç äéÜñêåéá ôçò äéáäéêáóßáò äçìéïõñãßáò ôïõò äßóêïõò äéáíïìÞò. Äçìéïõñãåß SETUP1A.MAK óå SETUP1.EXE, óõìðéÝæåé ôïí êáé áíôéãñÜöåé ôïõò äßóêïõò äéáíïìÞò. ¼ôáí SETUP.EXE áðü ôïõò äßóêïõò äéáíïìÞò, ôá áñ÷åßá óôï SETUP.LST áíôéãñÜöïíôáé óôïí õðïëïãéóôÞ ðñïïñéóìïý. SETUP1.EX_ åßíáé ÷ùñßò óõìðßåóç êáé íá åêôåëåóôïýí ãéá íá îåêéíÞóåôå ôçí áíôéãñáöÞ áñ÷åßùí áðü ôéò äéóêÝôåò óôïí õðïëïãéóôÞ ðñïïñéóìïý.

Åßíáé äõíáôü íá óôç óõíÝ÷åéá ôñïðïðïéÞóôå SETUP1A.MAK, áíáäüìçóç SETUP1.EXE, óõìðéÝóåôå êáé áíôéãñÜøôå ôïõò äßóêïõò äéáíïìÞò. Ãéá íá åîáóöáëßóåôå üôé ôï ìÝãåèïò ôïõ óõìðéåóìÝíïõ áñ÷åßïõ èá ÷ùñÜåé óôï ðñþôï äßóêï äéáíïìÞò, ðñÝðåé íá óõìðëÞñùóç ôïõ Ýñãïõ ìå êùäéêü ðñéí áðü ôçí ðñþôç åêôÝëåóç ôïõ "Ïäçãïý åãêáôÜóôáóçò". Then you can change the code into comments and add new code to prompt for the ODBC Setup disk. The resulting EXE size will then still fit on the first distribution floppy disk.

Modify SETUP1.FRM in the \VB\SETUPKIT\SETUP1 directory to add the necessary code to pad the executable. This file is copied into SETUP1A.MAK during the Setup Wizard's execution.

ÓÇÌÅÉÙÓÇ: Microsoft Technical Support does not support the modification of the Setup process or any of the setup files. Support is provided for the Setup Wizard and the files it creates on an "as is" basis only.

Here are the steps to follow:

1. Start Visual Basic and from the File menu, choose Open Project. Open SETUP1.MAK in the \VB\SETUPKIT\SETUP directory.
2. Select SETUP1.FRM from the project window. Press F7 to view the code.
3. At the end of the Form_Load procedure add the following code in the ExitSub: label part, after RestoreProgMan and before the End statement:

         Dim tmpK As String
         Dim tmpS As String
         Dim I As Long
         tmpK = "dummy"
         For I = 1 To 1000
            tmpS = Mid$(tmpK, 1, 2)
            tmpS = Mid$(tmpK, 1, 2)
            tmpS = Mid$(tmpK, 1, 2)
            tmpS = Mid$(tmpK, 1, 2)
            tmpS = Mid$(tmpK, 1, 2)
            tmpS = Mid$(tmpK, 1, 2)
            tmpS = Mid$(tmpK, 1, 2)
            tmpS = Mid$(tmpK, 1, 2)
            tmpS = Mid$(tmpK, 1, 2)
            tmpS = Mid$(tmpK, 1, 2)
            tmpS = Mid$(tmpK, 1, 2)
            tmpS = Mid$(tmpK, 1, 2)
            tmpS = Mid$(tmpK, 1, 2)
            tmpS = Mid$(tmpK, 1, 2)
            tmpS = Mid$(tmpK, 1, 2)
            tmpS = Mid$(tmpK, 1, 2)
            tmpS = Mid$(tmpK, 1, 2)
            tmpS = Mid$(tmpK, 1, 2)
            tmpS = Mid$(tmpK, 1, 2)
            tmpS = Mid$(tmpK, 1, 2)
         Next I

4. Save the project (ALT, F, V).
5. Run the Setup Wizard, and create the distribution disks.

Once the disks have been created, you need to go back into Visual Basic, edit SETUP1A.MAK, and add the appropriate code to prompt for the ODBC Setup And Installation Disk. ÁêïëïõèÞóôå ôá åîÞò âÞìáôá:

1. Ç åêêßíçóç ôçò Visual Basic.
2. Open the SETUP1A.MAK project in \VB\SETUPKIT\SETUP1 (ALT, F, O).
3. Choose SETUP1A.FRM and press F7 to view the code.
4. In the Form_Load procedure, place an apostrophe in front of each line of the dummy code that was previously inserted as a place holder:

         'Dim tmpK As String
         'Dim tmpS As String
         'Dim I As Long
         'tmpK = "dummy"
         'For I = 1 To 1000
         '   tmpS = Mid$(tmpK, 1, 2)
         '   tmpS = Mid$(tmpK, 1, 2)
         '   tmpS = Mid$(tmpK, 1, 2)
         '   tmpS = Mid$(tmpK, 1, 2)
         '   tmpS = Mid$(tmpK, 1, 2)
         '   tmpS = Mid$(tmpK, 1, 2)
         '   tmpS = Mid$(tmpK, 1, 2)
         '   tmpS = Mid$(tmpK, 1, 2)
         '   tmpS = Mid$(tmpK, 1, 2)
         '   tmpS = Mid$(tmpK, 1, 2)
         '   tmpS = Mid$(tmpK, 1, 2)
         '   tmpS = Mid$(tmpK, 1, 2)
         '   tmpS = Mid$(tmpK, 1, 2)
         '   tmpS = Mid$(tmpK, 1, 2)
         '   tmpS = Mid$(tmpK, 1, 2)
         '   tmpS = Mid$(tmpK, 1, 2)
         '   tmpS = Mid$(tmpK, 1, 2)
         '   tmpS = Mid$(tmpK, 1, 2)
         '   tmpS = Mid$(tmpK, 1, 2)
         '   tmpS = Mid$(tmpK, 1, 2)
         'Next I

5. Add the following code within the Form_Load procedure immediately following the commented code:

         x% = MsgBox("Do you want to install the ODBC Drivers?", 36,
            App.title)
         If x% = 6 Then
            If Not PromptForNextDisk(2, SourcePath$ + "ODBCADM.EX_") Then
               GoTo ErrorSetup
            End If
            x% = Shell(SourcePath$ & "setup.exe")
         End If

6. Change the disk number to 1 greater than the total number of distribution disks created. The disk number is the first parameter to the PromptForNextDisk procedure. In this example, the next disk to prompt for is 2.
7. Save the SETUP1A.MAK project and create the executable as SETUP1.EXE in the \VB\SETUPKIT\SETUP1 directory (ALT, F, K).
8. Shell out to an MS-DOS command prompt and change the directory to \VB\SETUPKIT\SETUP1. Execute the following at the command prompt:
   \VB\SETUPKIT\KITFILES\COMPRESS -r SETUP1.EXE
9. Place the first distribution floppy disk in the appropriate drive and copy SETUP1.EX_ to the floppy disk:
   copy SETUP1.EX_ A:\SETUP1.EX_

Now, when your distribution disks are run, the final step will be to prompt for the ODBC Setup and Installation disk. SETUP.EXE will be executed from this disk and the user can then install the appropriate ODBC driver and create the necessary Data Source. You should include instructions for this process.

For more information on modifying SETUP1.EXE please refer to Chapter 25, "Distributing Your Application" in the Microsoft Visual Basic Programmer's Guide.

RegisterDatabase

Visual Basic provides the RegisterDatabase statement to help in installing ODBC data sources, not drivers. The RegisterDatabase statement assumes that ODBCINST.INI and ODBCINST.DLL already exist on the computer. That is, the drivers must be installed before running RegisterDatabase. If so, the developer can use RegisterDatabase to add or update an entry in the ODBC.INI.

The problem with this method is that if the client computer does not have ODBC installed on the computer, the ODBCINST.INI and DLL will not exist. Also, if the ODBC driver is new to the computer, there will not be an entry for it in ODBCINST.INI, so RegisterDatabase will fail then as well.

The following description, syntax, remarks, and example about the RegisterDatabase statement come from the Visual Basic online Help:

ÐåñéãñáöÞ:Syntax:Remarks: The RegisterDatabase statement has the following parts:

• DSN: A string expression that is a name used in the OpenDatabase function and refers a block of descriptive information about the data source. For example, if the data source is an ODBC remote database, it would be the name of the server.
• DRIVER: A string expression that is the name of the ODBC driver. This is not the name of the ODBC driver DLL file. For example, "SQL Server" or "Oracle" are driver name but "SQLSRVR.DLL" is the name of a DLL file. You must have ODBC and the appropriate driver already installed.
• SILENT: A numeric expression that is True if you do not want to display the ODBC driver dialogs that prompt for driver-specific information, or False if you do want to display the ODBC driver dialogs. If silent is True, then attributes must contain all the necessary driver-specific information or the dialog will appear anyway.
• ATTRIBUTES: String expression that is a list of keywords to be added to the ODBC.INI file. The keywords are in a carriage-return delimited string.

ÐáñÜäåéãìá:If the database is already registered in the ODBC.INI file, the entry is updated. If RegisterDatabase fails for any reason, no changes are made to the ODBC.INI file and an error occurs.

ODBC API

This is probably the most flexible and most efficient method, but most developers are not familiar with it and do not have the ODBC SDK that documents the API. Developers should get the Microsoft Software Development Kit (SDK) and get the "Microsoft ODBC 2.0 Programmer's Reference and SDK Guide" from Microsoft Press.

Copy INI

If the developer is certain that an ODBC.INI and ODBCINST.INI do not exist on the installation computer, they can simply copy the files. However, the developer must ensure that the paths to the drivers are correct; paths are fully qualified within the .INI files. For example, the ODBC.INI file will specify C:\WINDOWS\SYSTEM\SQLSRVR.DLL as the driver for SQL Server, so if the user's Windows setup is in \WIN31, the path won't work.