you make it clear, thank's for the explanation. i didn't had any idea the differences. i used myODBC sometime before starting the .net provider (the old bytefx)

----- Original Message ----- From: SGr...@unimin.com To: Jorge Bastos Cc: dot...@lists.mysql.com Sent: Wednesday, January 12, 2005 9:44 PM Subject: Re: How do you create a DSN using ByteFX?

The difference between ODBC and Connector.NET is like the difference between
any two automobiles. Both are data access libraries but their interfaces (the
objects, methods, and properties exposed by a program or library) are totally
different, just as any two cars perform the same basic function (transportation)
but can have two totally different sets of controls (manual/automatic
transmission, power/manual steering, etc...)

ODBC is actually a Micro$oft specification that attempts to homogenize all
databases to "appear" the same. That is the actual purpose of an ODBC driver, to
translate the unique and individual access methods of each database into a
specific set of common objects, methods, and properties. Any library that can
sit on top of a database that allows you to use the ODBC interface to use that
database could be an ODBC driver (assuming you meet the other MS
requirements,too).

The Connector.NET library is a completely separate library that also
translates the interaction with a MySQL server to a set of objects, methods, and
properties. However, because the Connector.NET library is not coded to a fixed
specification (like ODBC) its developer is free to use whatever object names,
method names, and property names he wants. Usually a library for a language like
.NET is written as a wrapper to an interface (usually distributed as a DLL)
written by the DB manufacturer (frequently written in C or C++ and very
"low-level"). These "wrapper" libraries will usually expose interfaces similar
to the underlying library provided by the manufacturer but they need to
translate between differences in variable storage and language-specific data
types. This is also true for the Connector.NET library. However, that is not the
only .NET library out there.

Did that make any sense? I can explain it in other ways if you like but that's
what came to me first.

Shawn Green Database Administrator Unimin Corporation - Spruce Pine

> well that is a complicated question at least for me, > i have some problems explaning myself > i'm sure someone else on the list will know. > > jorge > > > ----- Original Message ----- > From: "Ahmet Erispaha" <ahme...@comcast.net> > To: "Jorge Bastos" <mysq...@decimal.pt> > Sent: Wednesday, January 12, 2005 6:43 PM > Subject: Re: How do you create a DSN using ByteFX? > > > > thanks. where can i get good info on difference between .net providers > and > > odbc providers? > > > > ----- Original Message ----- > > From: "Jorge Bastos" <mysq...@decimal.pt> > > To: "Ahmet Erispaha" <ahme...@comcast.net> > > Sent: Wednesday, January 12, 2005 1:37 PM > > Subject: Re: How do you create a DSN using ByteFX? > > > > > > > yap > > > > > > ----- Original Message ----- > > > From: "Ahmet Erispaha" <ahme...@comcast.net> > > > To: "Jorge Bastos" <mysq...@decimal.pt> > > > Sent: Wednesday, January 12, 2005 6:20 PM > > > Subject: Re: How do you create a DSN using ByteFX? > > > > > > > > > > Is that the MySQL ODBC 3.51 driver? > > > > > > > > ----- Original Message ----- > > > > From: "Jorge Bastos" <mysq...@decimal.pt> > > > > To: <dot...@lists.mysql.com> > > > > Sent: Wednesday, January 12, 2005 1:17 PM > > > > Subject: Re: How do you create a DSN using ByteFX? > > > > > > > > > > > >> you have to use myODBC > > > >> bytefx is a .net provider not a odbc one > > > >> > > > >> > > > >> > > > >> ----- Original Message ----- > > > >> From: "Ahmet Erispaha" <ahme...@comcast.net> > > > >> To: <dot...@lists.mysql.com> > > > >> Sent: Wednesday, January 12, 2005 6:13 PM > > > >> Subject: How do you create a DSN using ByteFX? > > > >> > > > >> > > > >> I have the ByteFX driver installed on my Windows 2000 machine. I'd > > like > > > > to > > > >> create a DSN which uses this driver as a data source but it's not on > > the > > > >> list of drivers when I go through the ODBC Data Source Administrator > > > > wizard > > > >> that sets up DSNs. > > > >> > > > >> Any suggestions? > > > >> > > > >> > > > >> -- > > > >> MySQL on .NET Mailing List > > > >> For list archives: http://lists.mysql.com/dotnet > > > >> To unsubscribe: > > > > http://lists.mysql.com/dotnet?unsub=ahme...@comcast.net > > > >> > > > > > > > > > > > > > > > -- > MySQL on .NET Mailing List > For list archives: http://lists.mysql.com/dotnet > To unsubscribe: http://lists.mysql.com/dotnet?unsub=sgr...@unimin.com >