Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 8 of 8 total
Thread ODBC v3.30 and VS 2003 C#
Tue, Feb 7 2006 11:46 PMPermanent Link

Kevin Kozlowski
I just purchased the ODBC driver and I'm trying to use it in a C# / VS 2003 project without much success. I've created an ODBC data
source that shows up in the ODBC Data Source Administration utility in XP (Control Panel > Data Sources) . I can access this data
source inside Excel.

In C#, I drop an OdbcDataAdapter control from the Data tab onto my form. A "Data Adapter Configuration Wizard" dialog displays. I
click Next, and then New Connection... which displays a Data Link Properities dialog. I then select the Provider tab, select "Microsoft
OLE DB Provider for ODBC Drivers" (it's the only one I see that references ODBC), and click Next. From the Connection tab, I select
my data source from the "Use data source name" combo box. I enter my user name and pass word, and I select my database from
the "Enter the initial catalog to use" combo box. There is a Test Connection button. If I click it, the message "Test connection
succeeded" displays.

I click OK, and then a warning dialog displays with the message "Unable to connect to database. Catastrophic failure."

I've tried different sequences of steps, but thus far, I've been unable to connect to my database (DBISAM v3.3 btw) via the ODBC
driver from C#. I'm using Visual Studio 2003 Professional.

I must be approaching this the wrong way. I'd appreciate any help in pointing me in the right direction.

Thanks,

-Kevin
Wed, Feb 8 2006 7:45 AMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Kevin,

<< I click OK, and then a warning dialog displays with the message "Unable
to connect to database. Catastrophic failure."  >>

What does the connection string look like that the connection wizard is
generating ?  I suspect that there's something funky in there.

--
Tim Young
Elevate Software
www.elevatesoft.com

Wed, Feb 8 2006 12:30 PMPermanent Link

Kevin Kozlowski
Tim,

Do you know where the connection string is located? I can't seem to find it.

-Kevin

----


"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote:

Kevin,

<< I click OK, and then a warning dialog displays with the message "Unable
to connect to database. Catastrophic failure."  >>

What does the connection string look like that the connection wizard is
generating ?  I suspect that there's something funky in there.

--
Tim Young
Elevate Software
www.elevatesoft.com

Thu, Feb 9 2006 11:23 AMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Kevin,

<< Do you know where the connection string is located? I can't seem to find
it. >>

It should be in your ODBCConnection component under the ConnectionString
property.

--
Tim Young
Elevate Software
www.elevatesoft.com

Thu, Feb 9 2006 11:59 AMPermanent Link

Kevin Kozlowski
Tim,

<<
It should be in your ODBCConnection component under the ConnectionString
property.
<<

Okay, I may be using the wrong set of components. I was using the OleDbConnection and OleDbDataAdapter. Should I instead be using
OdbcConnection and OdbcDataAdapter?

-Kevin
Fri, Feb 10 2006 2:43 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Kevin,

<< Okay, I may be using the wrong set of components. I was using the
OleDbConnection and OleDbDataAdapter. Should I instead be using
OdbcConnection and OdbcDataAdapter? >>

Sorry about not picking up on that.  Yes, those would be the best option.
The OLEDB-->ODBC bridge is a bit dodgy, and the ODBC data provider
components work great.

--
Tim Young
Elevate Software
www.elevatesoft.com

Sat, Feb 11 2006 5:55 PMPermanent Link

Kevin Kozlowski
Tim,

<< Sorry about not picking up on that.  Yes, those would be the best option.
The OLEDB-->ODBC bridge is a bit dodgy, and the ODBC data provider
components work great. >>

That's the ticket. The ODBC components work perfectly.

Are there instructions anywhere on what files need to be deployed with an app that uses the DBISAM ODBC drivers? After running
the installer, there is a Help folder, but it is empty so I'm not sure if you supply any documentation that may describe this.

Thanks,

-Kevin
Mon, Feb 13 2006 11:38 AMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Kevin,

<< Are there instructions anywhere on what files need to be deployed with an
app that uses the DBISAM ODBC drivers? After running
the installer, there is a Help folder, but it is empty so I'm not sure if
you supply any documentation that may describe this. >>

There should be a WinHelp file in there for the ODBC driver.  As for
deployment, you need to deploy the dbodbc.dll file and the following
registry entries need to be made:

Root: HKLM; SubKey: "Software\ODBC\ODBCINST.INI\DBISAM 3 ODBC Driver";
ValueType: string; ValueName: "APILevel"; ValueData: "1"; Flags:
uninsdeletekey
Root: HKLM; SubKey: "Software\ODBC\ODBCINST.INI\DBISAM 3 ODBC Driver";
ValueType: string; ValueName: "ConnectFunctions"; ValueData: "YYY"; Flags:
uninsdeletekey
Root: HKLM; SubKey: "Software\ODBC\ODBCINST.INI\DBISAM 3 ODBC Driver";
ValueType: string; ValueName: "Driver"; ValueData:
"{app}\lib\dbodbc\dbodbc.dll"; Flags: uninsdeletekey
Root: HKLM; SubKey: "Software\ODBC\ODBCINST.INI\DBISAM 3 ODBC Driver";
ValueType: string; ValueName: "DriverODBCVer"; ValueData: "03.00"; Flags:
uninsdeletekey
Root: HKLM; SubKey: "Software\ODBC\ODBCINST.INI\DBISAM 3 ODBC Driver";
ValueType: string; ValueName: "FileExtns"; ValueData: "*.dat,*.idx,*.blb";
Flags: uninsdeletekey
Root: HKLM; SubKey: "Software\ODBC\ODBCINST.INI\DBISAM 3 ODBC Driver";
ValueType: string; ValueName: "FileUsage"; ValueData: "1"; Flags:
uninsdeletekey
Root: HKLM; SubKey: "Software\ODBC\ODBCINST.INI\DBISAM 3 ODBC Driver";
ValueType: string; ValueName: "SQLLevel"; ValueData: "0"; Flags:
uninsdeletekey
Root: HKLM; SubKey: "Software\ODBC\ODBCINST.INI\DBISAM 3 ODBC Driver";
ValueType: string; ValueName: "Setup"; ValueData:
"{app}\lib\dbodbc\dbodbc.dll"; Flags: uninsdeletekey
Root: HKLM; SubKey: "Software\ODBC\ODBCINST.INI\DBISAM 3 ODBC Driver";
ValueType: dword; ValueName: "UsageCount"; ValueData: "1"; Flags:
uninsdeletekey
Root: HKLM; SubKey: "Software\ODBC\ODBCINST.INI\ODBC Drivers"; ValueType:
string; ValueName: "DBISAM 3 ODBC Driver"; ValueData: "Installed"; Flags:
uninsdeletevalue

If you're deploying the read-only driver (from the \lib\dbodbc\ro
installation subdirectory), then the following registry entries need to be
made:

Root: HKLM; SubKey: "Software\ODBC\ODBCINST.INI\DBISAM 3 ODBC Driver
(Read-Only)"; ValueType: string; ValueName: "APILevel"; ValueData: "1";
Flags: uninsdeletekey
Root: HKLM; SubKey: "Software\ODBC\ODBCINST.INI\DBISAM 3 ODBC Driver
(Read-Only)"; ValueType: string; ValueName: "ConnectFunctions"; ValueData:
"YYY"; Flags: uninsdeletekey
Root: HKLM; SubKey: "Software\ODBC\ODBCINST.INI\DBISAM 3 ODBC Driver
(Read-Only)"; ValueType: string; ValueName: "Driver"; ValueData:
"{app}\lib\dbodbc\ro\dbodbc.dll"; Flags: uninsdeletekey
Root: HKLM; SubKey: "Software\ODBC\ODBCINST.INI\DBISAM 3 ODBC Driver
(Read-Only)"; ValueType: string; ValueName: "DriverODBCVer"; ValueData:
"03.00"; Flags: uninsdeletekey
Root: HKLM; SubKey: "Software\ODBC\ODBCINST.INI\DBISAM 3 ODBC Driver
(Read-Only)"; ValueType: string; ValueName: "FileExtns"; ValueData:
"*.dat,*.idx,*.blb"; Flags: uninsdeletekey
Root: HKLM; SubKey: "Software\ODBC\ODBCINST.INI\DBISAM 3 ODBC Driver
(Read-Only)"; ValueType: string; ValueName: "FileUsage"; ValueData: "1";
Flags: uninsdeletekey
Root: HKLM; SubKey: "Software\ODBC\ODBCINST.INI\DBISAM 3 ODBC Driver
(Read-Only)"; ValueType: string; ValueName: "SQLLevel"; ValueData: "0";
Flags: uninsdeletekey
Root: HKLM; SubKey: "Software\ODBC\ODBCINST.INI\DBISAM 3 ODBC Driver
(Read-Only)"; ValueType: string; ValueName: "Setup"; ValueData:
"{app}\lib\dbodbc\ro\dbodbc.dll"; Flags: uninsdeletekey
Root: HKLM; SubKey: "Software\ODBC\ODBCINST.INI\DBISAM 3 ODBC Driver
(Read-Only)"; ValueType: dword; ValueName: "UsageCount"; ValueData: "1";
Flags: uninsdeletekey
Root: HKLM; SubKey: "Software\ODBC\ODBCINST.INI\ODBC Drivers"; ValueType:
string; ValueName: "DBISAM 3 ODBC Driver (Read-Only)"; ValueData:
"Installed"; Flags: uninsdeletevalue

BTW, these entries are from our Inno Setup installation script for the ODBC
driver.

If you need the data source configuration registry entries, you can find
them here:

http://www.elevatesoft.com/dbisam4odbc_registry_entries.htm

Normally, these are set up when the data source is added using the ODBC Data
Sources configuration wizard in Windows XP, but you can also set them up
programmatically as needed.

--
Tim Young
Elevate Software
www.elevatesoft.com

Image