Andre
Thu Oct 27 13:14:28 CDT 2005
Pascal wrote:
It's important to understand which kind of DSN you have. On an x64 system,
you can create an ODBC connection(DSN) on the 32-bit side of the system or
on the 64-bit side of the system.
32-bit applications will only see ODBC connections created in the 32-bit
side, and 64-bits applications will only see ODBC connections from the
64-bit side. Each kind of application has is own registry.
To setup DSN for 32-bit application you must use:
%WINDIR%\SysWOW64\odbcad32.exe
and for 64-bit application you must use:
%WINDIR%\System32\odbcad32.exe
There is not 32-bit edition of Windows XP on the XP Pro x64 media. Have you
contacted Veritas about any future updates to support x64?
--
Andre
Extended64 |
http://www.extended64.com
Blog |
http://www.extended64.com/blogs/andre
http://spaces.msn.com/members/adacosta
FAQ for MS AntiSpy
http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm
"He1b" <heebe@hotmail.com> wrote in message
news:1130436496.095755.141990@g49g2000cwa.googlegroups.com...
> I'm running Windows 64 bit OS on a Dell 2850 Xeon system. I am
> starting to regret going to 64 bit as this OS does not seem ready for
> prime time. First, my SQL connection does not work on my ASP
> application (it works fine in Windows 2000 Srv). The error message I
> get using DSN or SQLOLEDB is:
>
> ADODB.Connection error '800a0ea9'
>
> Provider is not specified and there is no designated default provider
>
> Again, no issues on Windows 2000. Also, my Veritas Backup Exec 9.1
> isn't compatible with 64 bit. Should I consider going back to 32 bit?
> Is there a way to install 32 bit over top of 64 bit (without wiping the
> box). Also, is a 32 bit version avaiable on the 64 bit media?
>
> Thanks in Advance
>