Definitive doc on connecting to SQL server (OpenInsight Specific)
At 14 JUL 1998 06:22:07AM Sedick Cloete wrote:
Is there a definitive document covering, exactly, how to implement the connection to a SQL server data source? It has to describe what drivers are required, what config settings, what problems could be expected, etc. We've gone through the connection to Access via ODBC, but it's still not operating 100%. Essentially what we have to achieve is a solid and stable Warehousing procedure, so there are no database bound forms, reports etc. Can anyone help?
At 14 JUL 1998 07:29AM Cameron Revelation wrote:
Sedick,
The steps to connecting with SQL Server:
1. Install the SQL Server client for 16-bit Windows (aka Windows 3.1)
2. Make sure the .\bin directory of the SQL Server client is in the path (so OpenInsight can find the db-library API which is in W3DBLIB.DLL)
3. Verify connection using the ISQL/W tool provided in the SQL Server client
4. Configure connection in OpenInsight (Client/Server Workspace, new Connection); only the Server name attribute is required to connect
5. Test the connection information with the OpenInsight Query Window (Client/Server Workspace, Tools menu) using the same login/password as you tested with ISQL/W
Note: A new patch is available in the Works Online section for the SQL Server Connection Object.
Regarding the problems you mentioned with Access, I assume that has to do with the 32-bit drivers on Windows 95?
Cameron Purdy
Revelation Software
At 14 JUL 1998 03:06PM Sedick Cloete wrote:
Thanks, Cameron, for your speedy and sensible-sounding response. No, our real problem with Access was working out how to write LH rows via ODBC (we got the 'thunking' document and it works). We got real confused with the plethora of functions available in OI, and our problem now is simply that we cannot get rows written to Access if those rows exist already (I'm sure a simple explanation exists). Thanks again.
At 15 JUL 1998 07:27AM Cameron Revelation wrote:
Sedick,
No, our real problem with Access was working out how to write LH rows via ODBC (we got the 'thunking' document and it works). We got real confused with the plethora of functions available in OI, and our problem now is simply that we cannot get rows written to Access if those rows exist already (I'm sure a simple explanation exists).
In SQL, there are two different ways to write: insert and update. In other word, the READ operation in BASIC+ is synonomous with the SQL SELECT statement, the DELETE operation in BASIC+ is synonomous with the SQL DELETE statement, but the WRITE operation in BASIC+ has two corresponding SQL constructs. If the row already exists, you must UPDATE it (which is theoretically identical to a delete immediately followed by an insert … in fact most SQL database implement it that way internally). If the row does not exist, you must INSERT it.
Am I on the right track?
Cameron Purdy
Revelation Software
At 17 JUL 1998 10:58AM Sedick Cloete wrote:
Yes, I think so. I'll get back to my code and see what I ended up doing. Thanks.
At 17 JUL 1998 11:01AM Sedick Cloete wrote:
Yes, I think so. I'll get back to my code and see what I ended up doing. Thanks.