32 bit SQLDMO code on a 64 bit server

Should an application written in VB6 and early bound to SQL Server 2000
SQLDMO run on a machine with 64 bit SQL Server 2000 installed?
We update SQL databases with a custom written in house VB6 app. What would
be involved in getting this program to run in this environment?
Thanks for any input.Hi
VB 6 is a 32 bit applicatzion and will not run on 64 bit Itanium I/II's as
the Itanium is a lot different in architecture to the existing 32 bit
processor.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Scott Duckworth" wrote:

> Should an application written in VB6 and early bound to SQL Server 2000
> SQLDMO run on a machine with 64 bit SQL Server 2000 installed?
> We update SQL databases with a custom written in house VB6 app. What would
> be involved in getting this program to run in this environment?
> Thanks for any input.
>
>|||Thanks for the info.
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:DF34C2FB-F59D-48F8-BBA5-D57339C384B9@.microsoft.com...
> Hi
> VB 6 is a 32 bit applicatzion and will not run on 64 bit Itanium I/II's as
> the Itanium is a lot different in architecture to the existing 32 bit
> processor.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
>
> "Scott Duckworth" wrote:
>
would|||There is such a thing as WOW64 hosts 32-bit Windows applications. If you are
not running Windows Server 2003 SP1, you should use the IA32 extension
layer.
However Microsoft does not support running the SQL Server 2000 tools in
WOW64 on Itanium, which does not mean it does not work, it does.
So you would have to install the 32-bit client tools on your Itanium, which
will get you SQL-DMO, then you need your VB6 application and VB6 runtime.
GertD@.SQLDev.Net
Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.
Copyright SQLDev.Net 1991-2005 All rights reserved.
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:DF34C2FB-F59D-48F8-BBA5-D57339C384B9@.microsoft.com...
> Hi
> VB 6 is a 32 bit applicatzion and will not run on 64 bit Itanium I/II's as
> the Itanium is a lot different in architecture to the existing 32 bit
> processor.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
>
> "Scott Duckworth" wrote:
>

2147467259 - [DBNETLIB][ConnectionWrite (send()).]General network

I Have SQL Express installed on 17 ships. Each ship has a VB6 Client
application using OLEDB to connect to the database on local machine. Other
workstations on network also connect - we think without error. The error
above is thrown on 4 of the 17 ships. The workstations acting as the file
server are supposed to be identical (Windows XP).
We have been assured that all poer save settings on LAN Card and motherboard
have been disabled.
If I google on this error, I get over 100 hits going back several years !
Ideas to fix have included turning off connection pooling and using TCPIP
instead of Named Pipes on client workstation where database server and
application are running.
Any other ideas on what could cause this, or why 13 machines are OK, but 4
are not ? Thanks.
Mark StoryPerhaps watching this might help:
http://support.microsoft.com/kb/875285/
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Mark Story" <MarkStory@.discussions.microsoft.com> wrote in message
news:E02C9E86-1EF3-40CD-8487-57B18A02BFCA@.microsoft.com...
>I Have SQL Express installed on 17 ships. Each ship has a VB6 Client
> application using OLEDB to connect to the database on local machine. Other
> workstations on network also connect - we think without error. The error
> above is thrown on 4 of the 17 ships. The workstations acting as the file
> server are supposed to be identical (Windows XP).
> We have been assured that all poer save settings on LAN Card and
> motherboard
> have been disabled.
> If I google on this error, I get over 100 hits going back several years !
> Ideas to fix have included turning off connection pooling and using TCPIP
> instead of Named Pipes on client workstation where database server and
> application are running.
> Any other ideas on what could cause this, or why 13 machines are OK, but 4
> are not ? Thanks.
>
> --
> Mark Story