This is a multi-part message in MIME format.



------=_NextPart_000_0201_01C10165.9DA51150

Content-Type: text/plain;

	charset="iso-8859-1"

Content-Transfer-Encoding: quoted-printable



As you may or may not know, odbc.NET was released yesterday.



http://www.microsoft.com/downloads/release.asp?ReleaseID=3D31125



Be aware that "out of the box" installation will not work

unless you reference the assembly name, over and above

referencing the namespace.



i.e.,



<%@ Import Namespace=3D"System.Data.Odbc" %>

does NOT work by itself.



You also need to reference the assembly's name :



<%@ Import Namespace=3D"System.Data.Odbc" %>

<%@ Assembly Name =3D "System.Data.Odbc" %>



Adding the following to the <compilation> <assemblies> section of 

machine.config,

will allow odbc.NET to work without an assembly name reference :



<add assembly=3D"System.Data.Odbc, Version=3D1.0.2411.0, 

Culture=3Dneutral, PublicKeyToken=3Db77a5c561934e089"/>



I wish they'd included a line, in the documentation, which specified 

that

the assembly has to be referenced, over and above importing the 

namespace.



Then again,

the examples don't include the <%@ Import Namespace=3D" ..." %> line, 

either...;>)



This is confusing, because all other System.* assemblies

only need for the namespace to be imported to work.



regards,





Juan T. Llibre

Microsoft MVP [IIS/ASP]

"Beginning ASP.NET", Wrox Press - Look for it in August!

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D