Installshield on the issue of ODBC packaging, urgent use! !! !! !! !! !! !! !!

potticfg

I use a set of small software developed by DELPHI, using ODBC as the database interface, but after making the installation disk and packaging, I need to manually set up ODBC on another machine to install, this is not good, I have found a lot of information, but to no avail. Any friend can help me tell me how to configure ODBC when packaging. Thank you very much.
I use SQL SERVER and installshield.
This is where installshield adds the user data source name, the server IP, the connected server database name Weal, the server database login name sa, and the password password.

albertq12

I also want to know this question.

zalinzhang

Make another configuration file and read from the configuration file
User data source name, server IP, connected server database name Weal, server database login name sa, password password.
Easy to change later.

njmumu

The odbc information is written in the registry, the location is at
RootKey = HKEY_LOCAL_MACHINE;
Software\\ODBC\\ODBC.INI
You can all add a few odbc connections, look at the registry to understand

WayWon

1. It is best to package MDAC directly when packaging, even without packaging, the operating system has been integrated
2. The ODBC alias can be established directly through the InstallShield registry, no special setting is required in InstallShield
The registry is set up in the Resources / Regristry Sets part of InstallShield, the specific establishment is
HKEY_CURRENT_USER\Software\ODBC\ODBC.INI
or
HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI
The specific choice depends on whether you are creating a user DSN or a system DSN. The specific content varies according to the database. You can copy it directly from your registry

potticfg

WayWon:
If I create a user DSN.
After this HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI, where to write the data source name, server IP, connected server database name Weal, server database login name sa, password password these messages.

potticfg

Can you give a detailed example?

WayWon

User DSN is here
HKEY_CURRENT_USER\Software\ODBC\ODBC.INI
User DSN is a directory in the registry, just copy this directory to InstallShield, the location of the copy is InstallShield Resources / Regristry Sets

Is this a detailed example?

fishead

[Registry]
Root: HKCU; SubKey: Software\ODBC\ODBC.INI\ODBC Data Sources; ValueType: string; ValueName: debug; ValueData: SQL Server; Flags: createvalueifdoesntexist uninsdeletevalue
Root: HKCU; SubKey: Software\ODBC\ODBC.INI\debug; Flags: createvalueifdoesntexist uninsdeletevalue; ValueName: Driver; ValueType: string; ValueData: c:\WINDOWS\system32\SQLSRV32.dll
Root: HKCU; SubKey: Software\ODBC\ODBC.INI\debug; Flags: createvalueifdoesntexist uninsdeletevalue; ValueName: Description; ValueType: string; ValueData: debug
Root: HKCU; SubKey: Software\ODBC\ODBC.INI\debug; Flags: createvalueifdoesntexist uninsdeletevalue; ValueName: Server; ValueType: string; ValueData: 192.168.250.200
Root: HKCU; SubKey: Software\ODBC\ODBC.INI\debug; Flags: createvalueifdoesntexist uninsdeletevalue; ValueName: LastUser; ValueType: string; ValueData: amu

potticfg

Where to write the data source name, the server's IP, the connected server database name Weal, the server database login name sa, password password. these messages.
I just don't understand.