SQL SERVER 7.0 IN WIN 98 WITH OI 3.2 (OpenInsight)
At 06 JUN 2000 06:27:45PM Josef Obregon wrote:
HI ALL!
I HAVE A PROBLEM, A COULD NOT CONNECT OI 3.7.2 WITH A SQL SERVER 7.0 INSTALLED IN MY PC WITH WIN 98 2EDITION.
WITH SQL 7.0 IN THE SERVER WORKS FINE , BUT WITH MY PC LIKE LOCAL SERVER DONT WORK, THE QUERY WINDOW IN THE CLIENT SERVER WORKSPACE PRESENTS A MESSAGE LIKE "UNABLE TO CONNECT:SQL SERVER IS UNAVAILABLE OR DOES NOT EXIST"
ANY IDEA?
THANKS IN ADVANCE..
At 07 JUN 2000 10:41AM Stephen S. Revelation wrote:
Josef,
At the least, I would run through this KnowledgeBase Article on connecting via ODBC to MSSQL7.
If that doesn't help you out, can you elaborate in much greater detail on what you have tried?
-Stephen
At 10 JUN 2000 10:21AM David Singer wrote:
We are having similar problems. We use 3.7.2
See "OI reading from SQL 7 into LH (David Singer 05/27/2000)" for a description of what we are doing. To summarize, we are able to hook OI to Access (ODBC) seeing tables in Access drawn from SQL7, but cannot see the SQL7 tables (ODBC).
Direct help (phone and email) from esteemed members of This Group have not been able to resolve this issue. They can make it work on their computers, we cannot on ours.
The primary question is "What component(s) is/are different between the installations?" A secondary question is "What component(s) is/are required by OI to be successful?" We have not found a person, a posting, nor a book with either answer. All efforts have only uncovered just one hint that some special DLLs *might* need to be loaded (but no indication from where these DLLs are to be taken, nor *which* version to employ).
Frustrating, to say the least. There has been quite a lot of dialog, none of which appears on this board and all of which seem to lead to dead ends.
The "best workaround" so far is to port all the tables to Access and skip SQL7 efforts. Not a robust solution, to be kind.
Folks, we don't believe the answer is to be found by searching the KB. Been there, done that. Have a lot of Tshirts and caps, but that particular game is rained out.
We are convinced there is a small but critical piece to the puzzle missing, and we'd love to have a total inventory of what pieces are in fact essential for full operation.
We are appealing for further help because, frankly, we can't get OI to work as advertised. Or maybe it's SQL7 which won't work as advertised. Regardless, neither product will ODBC with the other but both will ODBC with Access.
David Singer