<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2653.12">
<TITLE>Re: Using Windows ODBC drivers</TITLE>
</HEAD>
<BODY>
<BR>
<P><FONT SIZE=2>> 5.14.2. Using Windows ODBC drivers</FONT>
<BR><FONT SIZE=2>> Does anyone actually have any experience of this and anything to add?</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> I do, with Microsoft Access and the JetProxy JDBC. If there's any </FONT>
<BR><FONT SIZE=2>> interest, I can give you a quick summary on how to set things up.</FONT>
</P>
<P><FONT SIZE=2>It looks like the stuff on WineHQ is a bit out of date.</FONT>
<BR><FONT SIZE=2>A patch I submitted in March added some info that Boaz</FONT>
<BR><FONT SIZE=2>put together. Now that section should read:</FONT>
</P>
<P><FONT SIZE=2> <title>Using Windows ODBC drivers</title></FONT>
<BR><FONT SIZE=2> <para></FONT>
<BR> <FONT SIZE=2> Native ODBC drivers have been reported to work for many types of </FONT>
<BR> <FONT SIZE=2> databases including MSSQL and Oracle. In fact, some like MSSQL can </FONT>
<BR><FONT SIZE=2> only be accessed on Linux through a Winelib app. Rather than</FONT>
<BR><FONT SIZE=2> just copying DLL files, most ODBC drivers require a Windows-based</FONT>
<BR><FONT SIZE=2> installer to run to properly configure things such as registry keys.</FONT>
<BR> <FONT SIZE=2></para></FONT>
<BR> <FONT SIZE=2><para></FONT>
<BR> <FONT SIZE=2> In order to set up MSSQL support you will first need to download</FONT>
<BR> <FONT SIZE=2> and run the mdac_typ.exe installer from microsoft.com. In order to </FONT>
<BR><FONT SIZE=2> configure your ODBC connections you must then run CLICONFG.EXE and </FONT>
<BR> <FONT SIZE=2> ODBCAD32.EXE under Wine. You can find them in the windows\system</FONT>
<BR><FONT SIZE=2> directory after mdac_typ runs. Compare the output of these programs</FONT>
<BR><FONT SIZE=2> with the output on a native Windows machine. Some things, such</FONT>
<BR><FONT SIZE=2> as protocols, may be missing because they rely on being installed</FONT>
<BR> <FONT SIZE=2> along with the operating system. If so, you may be able to copy</FONT>
<BR><FONT SIZE=2> missing functionality from an existing Windows installation as</FONT>
<BR><FONT SIZE=2> well as any registry values required. A native Windows installation</FONT>
<BR><FONT SIZE=2> configured to be used by Wine should work the same way it did</FONT>
<BR><FONT SIZE=2> when run natively.</FONT>
</P>
<P><FONT SIZE=2>If you'd like to make any additions or corrections, please</FONT>
<BR><FONT SIZE=2>work from the version in CVS. If you'd like me to do the</FONT>
<BR><FONT SIZE=2>SGML markup, feel free to email me raw text to add. If so,</FONT>
<BR><FONT SIZE=2>no rush - I'll be out of town till May 10th.</FONT>
</P>
<P><FONT SIZE=2>Thanks!</FONT>
</P>
<P><FONT SIZE=2>---------------</FONT>
<BR><FONT SIZE=2>Brian Vincent</FONT>
<BR><FONT SIZE=2>Copper Mountain Telecom</FONT>
<BR><FONT SIZE=2>vincentb@coppercolorado.com</FONT>
</P>
</BODY>
</HTML>