ODBC Driver development

Hi everybody,
I want to develop an ODBC driver to connect a normal windows application to
a middleware product.
I can't find any examples or hints with regard to ODBC driver development.
Here are the questions:
- Does anybody have experience with ODBC driver development?
- Can anybody provide me with an example of (rudimentary) ODBC driver code?
- Any hints / documentation tips / experiences?
Thanks already.
Kindest Regards,
Arthur.You may want to start by reviewing the ODBC Programmers Reference at:
http://msdn.microsoft.com/library/e...this_manual.asp
-Sue
On Thu, 3 Jun 2004 15:57:00 +0200, "Arthur van Rossum"
<arthurvanrossum@.mail.com> wrote:

>Hi everybody,
>I want to develop an ODBC driver to connect a normal windows application to
>a middleware product.
>I can't find any examples or hints with regard to ODBC driver development.
>Here are the questions:
>- Does anybody have experience with ODBC driver development?
>- Can anybody provide me with an example of (rudimentary) ODBC driver code?
>- Any hints / documentation tips / experiences?
>Thanks already.
>Kindest Regards,
>Arthur.
>|||Thank you Sue.
I have been browsed through this documentation.
Gives some more insight.
I'm still interrested in sample code etc.
Cheers,
Arthur.
"Sue Hoegemeier" <Sue_H@.nomail.please> schreef in bericht
news:k7hub09ev6ff65260iddc294f4h8k61ceq@.
4ax.com...
> You may want to start by reviewing the ODBC Programmers Reference at:
> http://msdn.microsoft.com/library/e...this_manual.asp
> -Sue
> On Thu, 3 Jun 2004 15:57:00 +0200, "Arthur van Rossum"
> <arthurvanrossum@.mail.com> wrote:
>
to[vbcol=seagreen]
development.[vbcol=seagreen]
code?[vbcol=seagreen]
>|||The ODBC SDK used to have samples - possibly the MDAC SDK
has some ODBC samples. The MDAC downloads and SDKs are
located at:
http://msdn.microsoft.com/data/mdac/default.aspx
-Sue
On Sat, 5 Jun 2004 17:40:23 +0200, "Arthur van Rossum"
<arthurvanrossum@.mail.com> wrote:

>Thank you Sue.
>I have been browsed through this documentation.
>Gives some more insight.
>I'm still interrested in sample code etc.
>Cheers,
>Arthur.
>
>"Sue Hoegemeier" <Sue_H@.nomail.please> schreef in bericht
> news:k7hub09ev6ff65260iddc294f4h8k61ceq@.
4ax.com...
>to
>development.
>code?
>

ODBC Driver development

Hi everybody,
I want to develop an ODBC driver to connect a normal windows application to
a middleware product.
I can't find any examples or hints with regard to ODBC driver development.
Here are the questions:
- Does anybody have experience with ODBC driver development?
- Can anybody provide me with an example of (rudimentary) ODBC driver code?
- Any hints / documentation tips / experiences?
Thanks already.
Kindest Regards,
Arthur.
You may want to start by reviewing the ODBC Programmers Reference at:
http://msdn.microsoft.com/library/en...his_manual.asp
-Sue
On Thu, 3 Jun 2004 15:57:00 +0200, "Arthur van Rossum"
<arthurvanrossum@.mail.com> wrote:

>Hi everybody,
>I want to develop an ODBC driver to connect a normal windows application to
>a middleware product.
>I can't find any examples or hints with regard to ODBC driver development.
>Here are the questions:
>- Does anybody have experience with ODBC driver development?
>- Can anybody provide me with an example of (rudimentary) ODBC driver code?
>- Any hints / documentation tips / experiences?
>Thanks already.
>Kindest Regards,
>Arthur.
>
|||Thank you Sue.
I have been browsed through this documentation.
Gives some more insight.
I'm still interrested in sample code etc.
Cheers,
Arthur.
"Sue Hoegemeier" <Sue_H@.nomail.please> schreef in bericht
news:k7hub09ev6ff65260iddc294f4h8k61ceq@.4ax.com... [vbcol=seagreen]
> You may want to start by reviewing the ODBC Programmers Reference at:
> http://msdn.microsoft.com/library/en...his_manual.asp
> -Sue
> On Thu, 3 Jun 2004 15:57:00 +0200, "Arthur van Rossum"
> <arthurvanrossum@.mail.com> wrote:
to[vbcol=seagreen]
development.[vbcol=seagreen]
code?
>
|||The ODBC SDK used to have samples - possibly the MDAC SDK
has some ODBC samples. The MDAC downloads and SDKs are
located at:
http://msdn.microsoft.com/data/mdac/default.aspx
-Sue
On Sat, 5 Jun 2004 17:40:23 +0200, "Arthur van Rossum"
<arthurvanrossum@.mail.com> wrote:

>Thank you Sue.
>I have been browsed through this documentation.
>Gives some more insight.
>I'm still interrested in sample code etc.
>Cheers,
>Arthur.
>
>"Sue Hoegemeier" <Sue_H@.nomail.please> schreef in bericht
>news:k7hub09ev6ff65260iddc294f4h8k61ceq@.4ax.com.. .
>to
>development.
>code?
>

ODBC DataSource name problem

Hi All
We have an application which is used the ODBC Data Source to comunicate
with the database. So during the installation of the product the
installation creating
the database name like : VAPost and server = datasource name which is 'VAPos
t'
not the real server name in the Microsoft SQL server DSN Configuration optio
n.
Also the installation is created the Alias in SQL Server Client Network
Utility for
'VAPost' which has Server alias = 'VAPost', NetWork library = 'TCP/IP' and
the Connection parameters is the ip address of the server.
So my application is used the DSN name 'VAPost' to connect to the database b
ut
there is an error message regarding "Communication Link Failure". I could
not figure out where is the problem but the same configuration it works on
other server. Any help is greatly appreciated.
Thanks,
JodieHi Jodie,
You are using a system DSN? You should access that DSN using a ".Net
Providers\ODBC data providers" Connection. Configure it to use the DSN.
Then within the dataflow, create a DataReader data source. Set it to use th
e
DSN connection. You control what is being pulled by the SQLCommand on the
second tab.
-Steven
"Jodie" wrote:

> Hi All
> We have an application which is used the ODBC Data Source to comunicate
> with the database. So during the installation of the product the
> installation creating
> the database name like : VAPost and server = datasource name which is 'VAP
ost'
> not the real server name in the Microsoft SQL server DSN Configuration opt
ion.
> Also the installation is created the Alias in SQL Server Client Network
> Utility for
> 'VAPost' which has Server alias = 'VAPost', NetWork library = 'TCP/IP' and
> the Connection parameters is the ip address of the server.
> So my application is used the DSN name 'VAPost' to connect to the database
but
> there is an error message regarding "Communication Link Failure". I could
> not figure out where is the problem but the same configuration it works on
> other server. Any help is greatly appreciated.
> Thanks,
> Jodie
>

ODBC Connection

Hi, All,
I got problem with ODBC connection, I have a product server and a stage
server, I made a sysdsn called SQLDSN, create a com+ called login and just a
very simply statement: list below:
private oconn as new adodb.connection
Public Function vPWD() As Boolean
Dim lngID As Long
Dim intTemp As Integer
Dim intPWD As Integer
Dim strSQL As String
Dim oRS As New ADODB.Recordset
Call startConn
oConn.spLogin strName & "," & strPWD, oRS
If oRS.BOF And oRS.EOF Then
vPWD = False
Else
vPWD = True
strOpCode = oRS.Fields("Opcode")
If IsNull(oRS.Fields("aop")) Then
bisOrg = False
Else
bisOrg = True
End If
End If
oRS.Close
Set oRS = Nothing
End Function
Private Sub startConn()
On Error GoTo err_handler
If Not bConnActive Then
oConn.Open strDSN
bConnActive = True
End If
Exit_function:
Exit Sub
err_handler:
Resume Exit_function
End Sub
and create a instance of login from asp page,
ODBC is tested working fine both stage and product
firewall is turned off on stage server.
connection timeout set to unlimited.
security context is fine.
from com debug, odbc connection is fine, both with stage and product
the problem is, when I change the odbc link server from product to stage run
the login.asp it does not work, and I got error message
ADODB.Connection (0x800A0E78)
Operation is not allowed when the object is closed.
anyone can help will be appreciated.
Thanks
Yifei
I found solution:
set com+ application security check at process level
Thanks
Yifei
"Yifei" <yjiang@.sdg.aust.com> wrote in message
news:eNmKDvJxFHA.3236@.TK2MSFTNGP14.phx.gbl...
> Hi, All,
> I got problem with ODBC connection, I have a product server and a stage
> server, I made a sysdsn called SQLDSN, create a com+ called login and just
a
> very simply statement: list below:
> private oconn as new adodb.connection
> Public Function vPWD() As Boolean
> Dim lngID As Long
> Dim intTemp As Integer
> Dim intPWD As Integer
> Dim strSQL As String
> Dim oRS As New ADODB.Recordset
> Call startConn
> oConn.spLogin strName & "," & strPWD, oRS
> If oRS.BOF And oRS.EOF Then
> vPWD = False
> Else
> vPWD = True
> strOpCode = oRS.Fields("Opcode")
> If IsNull(oRS.Fields("aop")) Then
> bisOrg = False
> Else
> bisOrg = True
> End If
> End If
> oRS.Close
> Set oRS = Nothing
> End Function
> Private Sub startConn()
> On Error GoTo err_handler
> If Not bConnActive Then
> oConn.Open strDSN
> bConnActive = True
> End If
> Exit_function:
> Exit Sub
> err_handler:
> Resume Exit_function
> End Sub
>
> and create a instance of login from asp page,
> ODBC is tested working fine both stage and product
> firewall is turned off on stage server.
> connection timeout set to unlimited.
> security context is fine.
> from com debug, odbc connection is fine, both with stage and product
> the problem is, when I change the odbc link server from product to stage
run
> the login.asp it does not work, and I got error message
> ADODB.Connection (0x800A0E78)
> Operation is not allowed when the object is closed.
> anyone can help will be appreciated.
> Thanks
> Yifei
>

ODBC Connection

Hi, All,
I got problem with ODBC connection, I have a product server and a stage
server, I made a sysdsn called SQLDSN, create a com+ called login and just a
very simply statement: list below:
private oconn as new adodb.connection
Public Function vPWD() As Boolean
Dim lngID As Long
Dim intTemp As Integer
Dim intPWD As Integer
Dim strSQL As String
Dim oRS As New ADODB.Recordset
Call startConn
oConn.spLogin strName & "," & strPWD, oRS
If oRS.BOF And oRS.EOF Then
vPWD = False
Else
vPWD = True
strOpCode = oRS.Fields("Opcode")
If IsNull(oRS.Fields("aop")) Then
bisOrg = False
Else
bisOrg = True
End If
End If
oRS.Close
Set oRS = Nothing
End Function
Private Sub startConn()
On Error GoTo err_handler
If Not bConnActive Then
oConn.Open strDSN
bConnActive = True
End If
Exit_function:
Exit Sub
err_handler:
Resume Exit_function
End Sub
and create a instance of login from asp page,
ODBC is tested working fine both stage and product
firewall is turned off on stage server.
connection timeout set to unlimited.
security context is fine.
from com debug, odbc connection is fine, both with stage and product
the problem is, when I change the odbc link server from product to stage run
the login.asp it does not work, and I got error message
ADODB.Connection (0x800A0E78)
Operation is not allowed when the object is closed.
anyone can help will be appreciated.
Thanks
YifeiI found solution:
set com+ application security check at process level
Thanks
Yifei
"Yifei" <yjiang@.sdg.aust.com> wrote in message
news:eNmKDvJxFHA.3236@.TK2MSFTNGP14.phx.gbl...
> Hi, All,
> I got problem with ODBC connection, I have a product server and a stage
> server, I made a sysdsn called SQLDSN, create a com+ called login and just
a
> very simply statement: list below:
> private oconn as new adodb.connection
> Public Function vPWD() As Boolean
> Dim lngID As Long
> Dim intTemp As Integer
> Dim intPWD As Integer
> Dim strSQL As String
> Dim oRS As New ADODB.Recordset
> Call startConn
> oConn.spLogin strName & "," & strPWD, oRS
> If oRS.BOF And oRS.EOF Then
> vPWD = False
> Else
> vPWD = True
> strOpCode = oRS.Fields("Opcode")
> If IsNull(oRS.Fields("aop")) Then
> bisOrg = False
> Else
> bisOrg = True
> End If
> End If
> oRS.Close
> Set oRS = Nothing
> End Function
> Private Sub startConn()
> On Error GoTo err_handler
> If Not bConnActive Then
> oConn.Open strDSN
> bConnActive = True
> End If
> Exit_function:
> Exit Sub
> err_handler:
> Resume Exit_function
> End Sub
>
> and create a instance of login from asp page,
> ODBC is tested working fine both stage and product
> firewall is turned off on stage server.
> connection timeout set to unlimited.
> security context is fine.
> from com debug, odbc connection is fine, both with stage and product
> the problem is, when I change the odbc link server from product to stage
run
> the login.asp it does not work, and I got error message
> ADODB.Connection (0x800A0E78)
> Operation is not allowed when the object is closed.
> anyone can help will be appreciated.
> Thanks
> Yifei
>sql