Is it necessary to edit the odbc.ini file when adding odbc drivers and connections?
It was a while ago I did this and I cant remember if I ever did edit the file or if I only made sure to have all the registry keys included in the package.

I deleted everything in my odbc.ini on the virtual image, rebooted it and to see if it had an impact on Wise. Wise worked fine.

But I need to be sure.
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
It's my understanding that only 16-bit ODBC drivers rely on the ODBC.INI file, all the 32-bit related settings are held in the registry instead.

If you know your environment does not have any 16-bit ODBC drivers, then there's no need to edit the ODBC.INI file.

Regards,

Spartacus
Answered 03/03/2009 by: spartacus
Black Belt

Please log in to comment
0
It's my understanding that only 16-bit ODBC drivers rely on the ODBC.INI file, all the 32-bit related settings are held in the registry instead.

Yep - for what it's worth.. I second this.
Answered 03/03/2009 by: MSIPackager
Third Degree Black Belt

Please log in to comment
0
Ok, thanks guys.
Answered 03/03/2009 by: polkagris
Orange Belt

Please log in to comment
0
If I were you, I'd avoid using Wise's ODBC handling and use simple Registry table entries instead. It's bitten me from time to time in the past and, since there's no real gain in using the ODBC tables, I've found it safer to avoid them.
Answered 03/03/2009 by: VBScab
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity