Over the last 18 months, I've put together an ASP intranet site to allow staff to access our internal CRM (Goldmine) via a user friendly interface with controls on data input. The database runs on a Borland Paradox dbase database. Connection into it via ODBC is fairly straight forward under ASP.

'Set up the SQL connection
Dim oConn
Set oConn = Server.CreateObject("ADODB.Connection")
oConn.Open "DSN=Goldmine"

creates a connection into the database via an ODBC DNS connection (that I've called "Goldmine") on the server.

It's also fairly easy to set up a connection via PHP:

$con = odbc_connect('Goldmine','','');

But I cannot get VB.NET (with Framework 1.1) to talk to the database. The straight forward code appears to be:

Dim objConnection As New ODBC.ODBCConnection("DSN=Goldmine")

But the connection fails. I've tried every variation (I can find on the web) of this connection object creation (including using OleDB object classes and pointing directly at the file/folder) but to no avail.

I have also set up a DSN to an access database and used the same ASP.NET code to connect to that, and that works fine. So I don't think it is code but rather the ADO.NET/ODBC drivers.

Using Framework 2.0 (Visual Studio 2005 Beta) it took me about 20 minutes to work out how to and create a working page, listing data from the database. However, .Net version 2 has crashed a couple of my systems and I'm not going to put it on a live server until it's out of beta (end of 2005 by the look of it).

<asp:SqlDataSource ID="SqlDataSource1" Runat="server" ProviderName="System.Data.Odbc"
ConnectionString="DSN=Goldmine" SelectCommand=strSelect>

is the relevant .Net 2 code created by VS2005.NET beta (the database creation tools are far easier to work with than with VS2003). However, Framework 1.1 doesn't seem to like this code.

Anyone any ideas of how I can get 1.1 to talk to the paradox database? Third party ODBC drivers perhaps?