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?
>
Showing posts with label develop. Show all posts
Showing posts with label develop. Show all posts
Wednesday, March 28, 2012
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?
>
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?
>
Monday, March 26, 2012
ODBC connections
I have been asked to develop some security software that includes detection
of what ODBC connections to SQL Server databases exist. I think that it is
not useful, at least for security purposes, to determine what ODBC
connections exist for a database. Am I wrong?
One reason it is not useful is that a connection can be created dynamicly
anytime. I know that, since I do it. The person asking for this project is
not familiar with such things but I have already explained this much to him.
I don't know about SQL Server security enough to be sure, but it is my
understanding that it has it's own security that is much more effective than
attempts to prevent access by limiting ODBC connections.
I am not asking what other solutions exist; if I am correct in what I say
here, then I will pursue the other solutions myself and when necessary in
another thread.>I have been asked to develop some security software that includes detection
>of what ODBC connections to SQL Server databases exist. I think that it is
>not useful, at least for security purposes, to determine what ODBC
>connections exist for a database. Am I wrong?
You are correct. The person requesting this may not be familiar with SQL
Server data access architecture and now it relates to security. ODBC is
just one data access API of many. There are also others, such as OLE DB,
SQL Native Client. It does not makes sense to me that one would care, at
least from a security perspective, which API is used to connect to SQL
Server. All APIs can access SQL Server without a pre-configured DSN.
> I don't know about SQL Server security enough to be sure, but it is my
> understanding that it has it's own security that is much more effective
> than attempts to prevent access by limiting ODBC connections.
Absolutely. SQL Server security is the primary place security needs to be
implemented. Logins, database users and object permissions all provide
various levels of security. Given a login with appropriate permissions, one
could write a simple VBScript using Notepad to access and manipulate
database data.
Hope this helps.
Dan Guzman
SQL Server MVP
"Sam Hobbs" <samuel@.social.rr.com_change_social_to_socal> wrote in message
news:%23GT8ACP%23FHA.3340@.TK2MSFTNGP12.phx.gbl...
>I have been asked to develop some security software that includes detection
>of what ODBC connections to SQL Server databases exist. I think that it is
>not useful, at least for security purposes, to determine what ODBC
>connections exist for a database. Am I wrong?
> One reason it is not useful is that a connection can be created dynamicly
> anytime. I know that, since I do it. The person asking for this project is
> not familiar with such things but I have already explained this much to
> him.
> I don't know about SQL Server security enough to be sure, but it is my
> understanding that it has it's own security that is much more effective
> than attempts to prevent access by limiting ODBC connections.
> I am not asking what other solutions exist; if I am correct in what I say
> here, then I will pursue the other solutions myself and when necessary in
> another thread.
>|||Yes, Dan, that definitely helps; thank you.
of what ODBC connections to SQL Server databases exist. I think that it is
not useful, at least for security purposes, to determine what ODBC
connections exist for a database. Am I wrong?
One reason it is not useful is that a connection can be created dynamicly
anytime. I know that, since I do it. The person asking for this project is
not familiar with such things but I have already explained this much to him.
I don't know about SQL Server security enough to be sure, but it is my
understanding that it has it's own security that is much more effective than
attempts to prevent access by limiting ODBC connections.
I am not asking what other solutions exist; if I am correct in what I say
here, then I will pursue the other solutions myself and when necessary in
another thread.>I have been asked to develop some security software that includes detection
>of what ODBC connections to SQL Server databases exist. I think that it is
>not useful, at least for security purposes, to determine what ODBC
>connections exist for a database. Am I wrong?
You are correct. The person requesting this may not be familiar with SQL
Server data access architecture and now it relates to security. ODBC is
just one data access API of many. There are also others, such as OLE DB,
SQL Native Client. It does not makes sense to me that one would care, at
least from a security perspective, which API is used to connect to SQL
Server. All APIs can access SQL Server without a pre-configured DSN.
> I don't know about SQL Server security enough to be sure, but it is my
> understanding that it has it's own security that is much more effective
> than attempts to prevent access by limiting ODBC connections.
Absolutely. SQL Server security is the primary place security needs to be
implemented. Logins, database users and object permissions all provide
various levels of security. Given a login with appropriate permissions, one
could write a simple VBScript using Notepad to access and manipulate
database data.
Hope this helps.
Dan Guzman
SQL Server MVP
"Sam Hobbs" <samuel@.social.rr.com_change_social_to_socal> wrote in message
news:%23GT8ACP%23FHA.3340@.TK2MSFTNGP12.phx.gbl...
>I have been asked to develop some security software that includes detection
>of what ODBC connections to SQL Server databases exist. I think that it is
>not useful, at least for security purposes, to determine what ODBC
>connections exist for a database. Am I wrong?
> One reason it is not useful is that a connection can be created dynamicly
> anytime. I know that, since I do it. The person asking for this project is
> not familiar with such things but I have already explained this much to
> him.
> I don't know about SQL Server security enough to be sure, but it is my
> understanding that it has it's own security that is much more effective
> than attempts to prevent access by limiting ODBC connections.
> I am not asking what other solutions exist; if I am correct in what I say
> here, then I will pursue the other solutions myself and when necessary in
> another thread.
>|||Yes, Dan, that definitely helps; thank you.
Friday, March 9, 2012
OCR Features
Hi All, is anyone had develop a system for OCR features? For example i wish to develop a system, all the data will input from fax machine. The fax machine need to scan the data and auto connect to PC software, is it this possible and accurate for the data ? Thank All !!!There are a number of tools for doing this. HP ships a package with at least some of their OfficeJet machines that does a respectable job. I'm pretty sure that Cannon does too, although I've never played with it myself.
Intel used to have a great product that they shipped with their SatisFAXion boards, that I think they've released as a commercial product. I don't know the name off the top of my head, but it was a great package (easy to use, accurate, and relatively low overhead).
I suspect that this market has already been pretty well developed. I'd be surprised if there was much room for real growth here.
-PatP
Intel used to have a great product that they shipped with their SatisFAXion boards, that I think they've released as a commercial product. I don't know the name off the top of my head, but it was a great package (easy to use, accurate, and relatively low overhead).
I suspect that this market has already been pretty well developed. I'd be surprised if there was much room for real growth here.
-PatP
Subscribe to:
Posts (Atom)