SQL Connectivity (OpenInsight 32-Bit) [Revelation On-Line Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
{{tag>category:"OpenInsight 32-Bit" author:"Martin Drenovac" author:"Bob Carten" author:"dsig@sigafoos.org"}}

[[https://www.revelation.com/the-works|Join The Works program to have access to the most current content, and to be able to ask questions and get answers from Revelation staff and the Revelation community]]


==== SQL Connectivity (OpenInsight 32-Bit) ====
=== At 15 MAR 2008 08:06:07AM Martin Drenovac wrote: ===
 
 
<QUOTE>
I've checked this forum prior to posting, so apologies if I might have missed something.

Am trying to set up an SQL Connection to my own local SQL server, and thru the C/S workspace Query windows - get a "Unable to connect to SQL" error message.



Under DOS, both the osql and sqlcmd commands must be primed with     -Shostname\SQLEXPRESS (in this case) -Usa -Ppassword - and both connect up.



I have tried both variations of the Connection setup with the host param having /not having the SQLEXPRESS portion. 



Can someone possibly help me with the connection setup.



TIA
</QUOTE>
----

=== At 15 MAR 2008 08:39AM Martin Drenovac wrote:  ===

<QUOTE>I've gone ahead and made an ODBC cnx to this server, and then gone back into C/S and made a cnx via ODBC - works perfectly.



But, I don't want ODBC.



Thanks again

</QUOTE>

----

=== At 16 MAR 2008 11:18PM Bob Carten wrote:  ===

<QUOTE>



Martin,

We have not updated the direct-connect drivers in some time.

They work with older versions of SqlServer whose direct connectivity is based on DBLIB.  Microsoft no longer supports DB-Lib connectivity.



See this post at [url=http://www.mydatabasesupport.com/forums/ms-sqlserver/219870-dblib.html]http://www.mydatabasesupport.com/forums/ms-sqlserver/219870-dblib.html[/url]



ODBC drivers used to be much slower than the direct connect drivers.  That is not longer true.

If you are using OpenInsight forms to edit Sql Data then you should just use the ODBC drivers. However, I find setting up ODBC connections is cumbersome. If I am passing data back and forth in programs then

I like to use OLE/DB drivers with ADO objects.  OLE/DB is Microsoft's acronym for the current generation of ODBC Driver; ADO is the acroynm for the OLE technology which supercedes the Connection object / Queryobject functions in OpenInsight. ADO is as a set of OLE objects.  I find it pretty easy to google for "ADO vbscript Example", find one that does what I want, then translate to OpenInsight's OLE syntax.  



I posted an example of [url=http://www.revelation.com/__85256DC1002A4A9E.nsf/0/D0FE0FC4C961B9C7852570B500689DE1?OpenDocument]How o update an Identity column in Mssql[/url] a while back.  I could post simpler examples if that would help.





HTH

- Bob

</QUOTE>

----

=== At 17 MAR 2008 12:18AM Martin Drenovac wrote:  ===

<QUOTE>Cheers Bob  - I will try these tonite, and get back to you.



So, will you rework the SQL interface or it's just a case of using the ODBC as the only mode forward?



I've just read your ADO article, and that might do me until my next stumble. 



Thank you very much.



</QUOTE>

----

=== At 17 MAR 2008 10:24AM Bob Carten wrote:  ===

<QUOTE>

Given that Microsoft has deprecated using direct-connect drivers, we have no plans to re-work the direct connect functionality.  Changing our dataset and data warehousing modules to use ADO would make more sense, but that is not in our schedule yet.



- Bob

</QUOTE>

----

=== At 17 MAR 2008 02:09PM dsig@sigafoos.org wrote:  ===

<QUOTE>As bob mentioned the odbc drivers are very fast and allow for connecting the the same way to multiple environments.

</QUOTE>


[[https://www.revelation.com/revweb/oecgi4p.php/O4W_HANDOFF?DESTN=O4W_RUN_FORM&INQID=WORKS_READ&SUMMARY=1&KEY=D8D7FBE2FACBE5448525740D00427A8E|View this thread on the Works forum...]]