Software Deployment

you don't say what the error is, but one thing I've found is that if you don't check for the odbc driver or have it installed on your packaging machine, wise packages will get errors if it just assumes the driver exists on the target machine and doesn't install it or check for it.

do a site search on odbc and you should find plenty of solutions. Some suggest simply doing the reg entries associated with the odbc data source, which might work most of the time, but assumes the existence of the associated driver which might or might not exist on the target machine. It's a little more work, but I'd rather use Windows Installer's built-in ODBC tables, especially if I've got a tool like Wise.

Sorry about that. All of these test are after the Pervasive 9.5 client has been installed. The only time I have gotten any error was when I tried to install the captured odbc settings. All of the other times it doesn't give an error. The settings just don't show up in the console. If I edit the registry & odbc.ini reboot. When I go back to the odbc console it still isn't there. But if I add it manually at this point it asks if I would like to overwrite the setting. Other then importing the settings into the .wsi or .mst how should I use the Windows Installer's built-in ODBC tables? Sorry if my question seems elementary.

Here is how I did one of our ODBC's, then I just pushed it out to everyone. Worked like a charm.


REGEDIT4

// Registry file generated by the Application Launcher.

[HKEY_LOCAL_MACHINE\SOFTWARE]

[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC]

[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI]

[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\ODBC Data Sources]
"Name of connection"="SQL Server"

[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\TDM_OLC_AdHocReporting]
"Driver"="%*WINSYSDIR%\\sqlsrv32.dll"
"LastUser"="<USERNAME (if applicable)>"
"Server"="<SERVERNAME>,<port#>"


ORIGINAL: dockland

Sorry about that. All of these test are after the Pervasive 9.5 client has been installed. The only time I have gotten any error was when I tried to install the captured odbc settings. All of the other times it doesn't give an error. The settings just don't show up in the console. If I edit the registry & odbc.ini reboot. When I go back to the odbc console it still isn't there. But if I add it manually at this point it asks if I would like to overwrite the setting. Other then importing the settings into the .wsi or .mst how should I use the Windows Installer's built-in ODBC tables? Sorry if my question seems elementary. Just to add to the confusion, I long ago abandonded using Wise's ODBC interface, preferring to export the relevant registry settings to a .REG and importing them into the project. As Owen suggests, you'll need to ensure the driver that is referred to is present.

In your testing - as ever - ProcMon will show you why errors are occuring. These will almost certainly be due to missing registry entry/entries or a missing/incorrectly-pathed driver.

Thanks Estes.
For some reason Wise wasn't picking up the [HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\ODBC Data Sources]

ORIGINAL: dockland

Thanks Estes.
For some reason Wise wasn't picking up the [HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\ODBC Data Sources]



Right on Dockland, glad to help.