From what i can tell 16 bit ODBC drivers and datasources are set in the windows/ODBC.ini and windows/ODBCINST.ini. With the 32bit drivers i am able to export the HKLM\Software\ODBC keys and import them into the project. This then builds the ODBC ini's properly. For my 16bit install i cant find any registry entries. So is the only way to really package my 16bit ODBC connections by adding the two ini's to the INI section in Wise's install expert? I use a 3rd party ODBC administrator to view the drivers rather then the 32bit on in Control Panel>Administrator>ODBC

Thanks,
Brandon
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
Hasn't anyone come across this before?
Answered 06/15/2005 by: schieb
Purple Belt

Please log in to comment
0
You say 3rd party? Borland?
Answered 06/16/2005 by: brenthunter2005
Fifth Degree Brown Belt

Please log in to comment
0
well no, what i mean is a 16bit ODBC Administrator gets installed to start>programs>ODBC. This is merely a veiwer. 3rd party was probably not the way i wanted to describe it.
Answered 06/16/2005 by: schieb
Purple Belt

Please log in to comment
0
That should be fine then. All you should need to do is add the required entries to the ODBC.INI (and ODBCINST.INI).

Have you already tried this and having issues?
Answered 06/17/2005 by: brenthunter2005
Fifth Degree Brown Belt

Please log in to comment
0
well yes i did that, then added the two .ini files to the INI section. I sometimes get unexpected errors. I was trying to figure out if it was because of the way i added the ODBC data sources and such, or if its just maybe a problem with running this old software on XP. Thanks for the replies, sorry i didn't follow up for so long
Answered 07/11/2005 by: schieb
Purple Belt

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