Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 6 of 6 total
Thread Connect VB.NET With ODBC v2
Tue, Oct 5 2010 10:26 PMPermanent Link

seba123neo

Hi, I'm trying to connect to tables with version 2.

I downloaded from another post the ODBC version 2.1

the DBIsamODBC.dll is version 2.1

I created a DSN called "mobiliza"

the code I'm using is:

Imports System.Data.Odbc

Public Class Form1

   Private Sub Form1_Load (ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load
       Try
         
           Dim Connection As New OdbcConnection ()
           Connection.ConnectionString = "DSN=mobiliza"
           Connection.Open()

           MsgBox ("connect")

           Connection.Close ()

       Catch ex As Exception
           MsgBox (ex.Message)
       End Try
   End Sub
End Class

the connection fails when it reaches the line "Connection.Open".

The error description is empty....

I have attached a table named Szonas.DAT

Thanks in advance.



Attachments: table.rar
Wed, Oct 6 2010 4:28 AMPermanent Link

Chris Holland

SEC Solutions Ltd.

Avatar

Team Elevate Team Elevate

Hi,

The tables appear to be fine.

Can you turn on the ODBC trace logging
(in the ODBC Data Source Administrator)
while you try and connect and post the log file please.

Also are you on a 32 or 64 bit machine?

Chris Holland
[Team Elevate]

On 06/10/2010 03:26, seba123neo wrote:
> Hi, I'm trying to connect to tables with version 2.
>
> I downloaded from another post the ODBC version 2.1
>
> the DBIsamODBC.dll is version 2.1
>
> I created a DSN called "mobiliza"
>
> the code I'm using is:
>
> Imports System.Data.Odbc
>
> Public Class Form1
>
>      Private Sub Form1_Load (ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load
>          Try
>
>              Dim Connection As New OdbcConnection ()
>              Connection.ConnectionString = "DSN=mobiliza"
>              Connection.Open()
>
>              MsgBox ("connect")
>
>              Connection.Close ()
>
>          Catch ex As Exception
>              MsgBox (ex.Message)
>          End Try
>      End Sub
> End Class
>
> the connection fails when it reaches the line "Connection.Open".
>
> The error description is empty....
>
> I have attached a table named Szonas.DAT
>
> Thanks in advance.
>

--
Chris Holland
[Team Elevate]
Wed, Oct 6 2010 8:22 AMPermanent Link

seba123neo

Thanks for the reply Chris...

the machine is Windows XP Service Pack 2...32 bits.

I activated the trace....the log is this.

WindowsApplicat 124-a50   ENTER SQLAllocHandle
      SQLSMALLINT                  1 <SQL_HANDLE_ENV>
      SQLHANDLE           00000000
      SQLHANDLE *         0131D16C

WindowsApplicat 124-a50   EXIT  SQLAllocHandle  with return code 0 (SQL_SUCCESS)
      SQLSMALLINT                  1 <SQL_HANDLE_ENV>
      SQLHANDLE           00000000
      SQLHANDLE *         0x0131D16C ( 0x04751788)

WindowsApplicat 124-a50   ENTER SQLSetEnvAttr
      SQLHENV             04751788
      SQLINTEGER                 200 <SQL_ATTR_ODBC_VERSION>
      SQLPOINTER          0x00000003
      SQLINTEGER                  -6

WindowsApplicat 124-a50   EXIT  SQLSetEnvAttr  with return code 0 (SQL_SUCCESS)
      SQLHENV             04751788
      SQLINTEGER                 200 <SQL_ATTR_ODBC_VERSION>
      SQLPOINTER          0x00000003 (BADMEM)
      SQLINTEGER                  -6

WindowsApplicat 124-a50   ENTER SQLSetEnvAttr
      SQLHENV             04751788
      SQLINTEGER                 201 <unknown>
      SQLPOINTER          [Unknown attribute 201]
      SQLINTEGER                  -6

WindowsApplicat 124-a50   EXIT  SQLSetEnvAttr  with return code 0 (SQL_SUCCESS)
      SQLHENV             04751788
      SQLINTEGER                 201 <unknown>
      SQLPOINTER          [Unknown attribute 201]
      SQLINTEGER                  -6

WindowsApplicat 124-a50   ENTER SQLAllocHandle
      SQLSMALLINT                  2 <SQL_HANDLE_DBC>
      SQLHANDLE           04751788
      SQLHANDLE *         0131D1FC

WindowsApplicat 124-a50   EXIT  SQLAllocHandle  with return code 0 (SQL_SUCCESS)
      SQLSMALLINT                  2 <SQL_HANDLE_DBC>
      SQLHANDLE           04751788
      SQLHANDLE *         0x0131D1FC ( 0x04751830)

WindowsApplicat 124-a50   ENTER SQLSetConnectAttrW
      SQLHDBC             04751830
      SQLINTEGER                 103 <SQL_ATTR_LOGIN_TIMEOUT>
      SQLPOINTER          0x0000000F
      SQLINTEGER                  -5

WindowsApplicat 124-a50   EXIT  SQLSetConnectAttrW  with return code 0 (SQL_SUCCESS)
      SQLHDBC             04751830
      SQLINTEGER                 103 <SQL_ATTR_LOGIN_TIMEOUT>
      SQLPOINTER          0x0000000F (BADMEM)
      SQLINTEGER                  -5

WindowsApplicat 124-a50   ENTER SQLDriverConnectW
      HDBC                04751830
      HWND                00000000
      WCHAR *             0x04719A38 [      -3] "******\ 0"
      SWORD                       -3
      WCHAR *             0x04719A38
      SWORD                        2
      SWORD *             0x00000000
      UWORD                        0 <SQL_DRIVER_NOPROMPT>

WindowsApplicat 124-a50   EXIT  SQLDriverConnectW  with return code -1 (SQL_ERROR)
      HDBC                04751830
      HWND                00000000
      WCHAR *             0x04719A38 [      -3] "******\ 0"
      SWORD                       -3
      WCHAR *             0x04719A38
      SWORD                        2
      SWORD *             0x00000000
      UWORD                        0 <SQL_DRIVER_NOPROMPT>

WindowsApplicat 124-a50   ENTER SQLGetDiagRecW
      SQLSMALLINT                  2
      SQLHANDLE           04751830
      SQLSMALLINT                  1
      SQLWCHAR *          0x01148B20 (NYI)
      SQLINTEGER *        0x0424E2CC
      SQLWCHAR *          0x01148318 (NYI)
      SQLSMALLINT               1024
      SQLSMALLINT *       0x0424E2D0

WindowsApplicat 124-a50   EXIT  SQLGetDiagRecW  with return code 100 (SQL_NO_DATA_FOUND)
      SQLSMALLINT                  2
      SQLHANDLE           04751830
      SQLSMALLINT                  1
      SQLWCHAR *          0x01148B20 (NYI)
      SQLINTEGER *        0x0424E2CC
      SQLWCHAR *          0x01148318 (NYI)
      SQLSMALLINT               1024
      SQLSMALLINT *       0x0424E2D0

WindowsApplicat 124-a00   ENTER SQLFreeHandle
      SQLSMALLINT                  2 <SQL_HANDLE_DBC>
      SQLHANDLE           04751830

WindowsApplicat 124-a00   EXIT  SQLFreeHandle  with return code 0 (SQL_SUCCESS)
      SQLSMALLINT                  2 <SQL_HANDLE_DBC>
      SQLHANDLE           04751830

WindowsApplicat 124-a00   ENTER SQLFreeHandle
      SQLSMALLINT                  1 <SQL_HANDLE_ENV>
      SQLHANDLE           04751788

WindowsApplicat 124-a00   EXIT  SQLFreeHandle  with return code 0 (SQL_SUCCESS)
      SQLSMALLINT                  1 <SQL_HANDLE_ENV>
      SQLHANDLE           04751788

Thanks..
Wed, Oct 6 2010 8:40 AMPermanent Link

seba123neo

how does the program called "DBISAM viewer" to open tables without use external libraries ??

http://www.sharewareconnection.com/dbisam-viewer.htm
Wed, Oct 6 2010 9:13 AMPermanent Link

Chris Holland

SEC Solutions Ltd.

Avatar

Team Elevate Team Elevate

I expect it is written using the VCL libabries but that they are linked
into the EXE so there is no need for external DLL's

Chris Holland
[Team Elevate]


On 06/10/2010 13:40, seba123neo wrote:
> how does the program called "DBISAM viewer" to open tables without use external libraries ??
>
> http://www.sharewareconnection.com/dbisam-viewer.htm
>

--
Chris Holland
[Team Elevate]
Wed, Oct 6 2010 9:15 AMPermanent Link

Chris Holland

SEC Solutions Ltd.

Avatar

Team Elevate Team Elevate

Hi,

Unfortunately that does not tell me much, only that it failed to connect
but there was no reason why.

The Version 2 ODBC driver is very limited in what it does (i.e. it has
never been tested in Visual Basic) is there any way that you can upgrade
the tables to V3 or V4 and try the ElevateSoft drivers as these are much
more compatible with other programs?

Chris Holland
[Team Elevate]

On 06/10/2010 13:22, seba123neo wrote:
> Thanks for the reply Chris...
>
> the machine is Windows XP Service Pack 2...32 bits.
>
> I activated the trace....the log is this.
>
> WindowsApplicat 124-a50   ENTER SQLAllocHandle
>       SQLSMALLINT                  1<SQL_HANDLE_ENV>
>       SQLHANDLE           00000000
>       SQLHANDLE *         0131D16C
>
> WindowsApplicat 124-a50   EXIT  SQLAllocHandle  with return code 0 (SQL_SUCCESS)
>       SQLSMALLINT                  1<SQL_HANDLE_ENV>
>       SQLHANDLE           00000000
>       SQLHANDLE *         0x0131D16C ( 0x04751788)
>
> WindowsApplicat 124-a50   ENTER SQLSetEnvAttr
>       SQLHENV             04751788
>       SQLINTEGER                 200<SQL_ATTR_ODBC_VERSION>
>       SQLPOINTER          0x00000003
>       SQLINTEGER                  -6
>
> WindowsApplicat 124-a50   EXIT  SQLSetEnvAttr  with return code 0 (SQL_SUCCESS)
>       SQLHENV             04751788
>       SQLINTEGER                 200<SQL_ATTR_ODBC_VERSION>
>       SQLPOINTER          0x00000003 (BADMEM)
>       SQLINTEGER                  -6
>
> WindowsApplicat 124-a50   ENTER SQLSetEnvAttr
>       SQLHENV             04751788
>       SQLINTEGER                 201<unknown>
>       SQLPOINTER          [Unknown attribute 201]
>       SQLINTEGER                  -6
>
> WindowsApplicat 124-a50   EXIT  SQLSetEnvAttr  with return code 0 (SQL_SUCCESS)
>       SQLHENV             04751788
>       SQLINTEGER                 201<unknown>
>       SQLPOINTER          [Unknown attribute 201]
>       SQLINTEGER                  -6
>
> WindowsApplicat 124-a50   ENTER SQLAllocHandle
>       SQLSMALLINT                  2<SQL_HANDLE_DBC>
>       SQLHANDLE           04751788
>       SQLHANDLE *         0131D1FC
>
> WindowsApplicat 124-a50   EXIT  SQLAllocHandle  with return code 0 (SQL_SUCCESS)
>       SQLSMALLINT                  2<SQL_HANDLE_DBC>
>       SQLHANDLE           04751788
>       SQLHANDLE *         0x0131D1FC ( 0x04751830)
>
> WindowsApplicat 124-a50   ENTER SQLSetConnectAttrW
>       SQLHDBC             04751830
>       SQLINTEGER                 103<SQL_ATTR_LOGIN_TIMEOUT>
>       SQLPOINTER          0x0000000F
>       SQLINTEGER                  -5
>
> WindowsApplicat 124-a50   EXIT  SQLSetConnectAttrW  with return code 0 (SQL_SUCCESS)
>       SQLHDBC             04751830
>       SQLINTEGER                 103<SQL_ATTR_LOGIN_TIMEOUT>
>       SQLPOINTER          0x0000000F (BADMEM)
>       SQLINTEGER                  -5
>
> WindowsApplicat 124-a50   ENTER SQLDriverConnectW
>       HDBC                04751830
>       HWND                00000000
>       WCHAR *             0x04719A38 [      -3] "******\ 0"
>       SWORD                       -3
>       WCHAR *             0x04719A38
>       SWORD                        2
>       SWORD *             0x00000000
>       UWORD                        0<SQL_DRIVER_NOPROMPT>
>
> WindowsApplicat 124-a50   EXIT  SQLDriverConnectW  with return code -1 (SQL_ERROR)
>       HDBC                04751830
>       HWND                00000000
>       WCHAR *             0x04719A38 [      -3] "******\ 0"
>       SWORD                       -3
>       WCHAR *             0x04719A38
>       SWORD                        2
>       SWORD *             0x00000000
>       UWORD                        0<SQL_DRIVER_NOPROMPT>
>
> WindowsApplicat 124-a50   ENTER SQLGetDiagRecW
>       SQLSMALLINT                  2
>       SQLHANDLE           04751830
>       SQLSMALLINT                  1
>       SQLWCHAR *          0x01148B20 (NYI)
>         SQLINTEGER *        0x0424E2CC
>       SQLWCHAR *          0x01148318 (NYI)
>         SQLSMALLINT               1024
>       SQLSMALLINT *       0x0424E2D0
>
> WindowsApplicat 124-a50   EXIT  SQLGetDiagRecW  with return code 100 (SQL_NO_DATA_FOUND)
>       SQLSMALLINT                  2
>       SQLHANDLE           04751830
>       SQLSMALLINT                  1
>       SQLWCHAR *          0x01148B20 (NYI)
>         SQLINTEGER *        0x0424E2CC
>       SQLWCHAR *          0x01148318 (NYI)
>         SQLSMALLINT               1024
>       SQLSMALLINT *       0x0424E2D0
>
> WindowsApplicat 124-a00   ENTER SQLFreeHandle
>       SQLSMALLINT                  2<SQL_HANDLE_DBC>
>       SQLHANDLE           04751830
>
> WindowsApplicat 124-a00   EXIT  SQLFreeHandle  with return code 0 (SQL_SUCCESS)
>       SQLSMALLINT                  2<SQL_HANDLE_DBC>
>       SQLHANDLE           04751830
>
> WindowsApplicat 124-a00   ENTER SQLFreeHandle
>       SQLSMALLINT                  1<SQL_HANDLE_ENV>
>       SQLHANDLE           04751788
>
> WindowsApplicat 124-a00   EXIT  SQLFreeHandle  with return code 0 (SQL_SUCCESS)
>       SQLSMALLINT                  1<SQL_HANDLE_ENV>
>       SQLHANDLE           04751788
>
> Thanks..
>

--
Chris Holland
[Team Elevate]
Image